search for: add_clang_librari

Hi, I am brand new to LLVM, or more precisely, trying to be. I'm getting stuck on compiling LLVM. - I tried installing on a Mint 18.1 VM with 6GB RAM, and the builds of some large executables were killed by the OOM killer. I finally realized that I needed to build using shared libraries, and succeeded. This was in November. - I put aside my LLVM project, and just got back to it. I got stuck

Hi, I've been doing some experimenting to get a "big" DLL version of Clang working. This involves changes to LLVM as well as Clang, and might apply to doing a "big" DLL version of LLVM too (if that makes sense), so I'm posting this to both cfe-dev and llvmdev. Basically, I want to find out if this mechanism is acceptable, or what alternative I should pursue. I have a

On Fri, Aug 04, 2017 at 01:54:33PM -0600, Jonathan Roelofs wrote: > > > On 8/4/17 1:14 PM, Goran Mekić via llvm-dev wrote: > > On Thu, Aug 03, 2017 at 08:22:24AM -0600, Jonathan Roelofs wrote: > > > IIUC, you don't want to cross compile llvm itself (which is what those > > > instructions are for), but instead you want to *use* llvm to cross compile > >

On Fri, Aug 04, 2017 at 04:03:35PM -0600, Jonathan Roelofs wrote: > > > 1) Pick a directory as your sysroot > > ~/arm-sysroot > > > > > 2) Install the libc headers there (without having built it) > > What I did was mv musl-*/include ~/arm-sysroot/usr/include. > > I think you need to copy them, not move them. On a new directories and fresh untar of musl, I

For a while now I have noticed that when I build LLVM using CMake on my OS X machine there are two dynamically linked libraries, BugpointPasses and LLVMHello, that are built with the extension ".so" instead of the extension ".dylib". This has been causing four test cases to fail when running "make check". The attached patch modifies add_llvm_loadable_module in the

I'm following the instructions here: http://clasg.llvm.org/get_started.html and, while running cmake, I get: > CMake Error at cmake/modules/LLVM-Config.cmake:141 (message): > Library `vectorize' not found in list of llvm libraries. > Call Stack (most recent call first): > cmake/modules/LLVM-Config.cmake:54 (explicit_map_components_to_libraries) >

Hi! I'm porting my own projects to CMake (seems very cool) and I want to import LLVM as external libraries. To simplify this CMake supports an export feature that can export an LLVM.cmake file that lists all libraries of LLVM. With this I could simplify the use of LLVM in my own CMake project. For this the following cmake files of LLVM have to be extended (patches are provided at the end of

Hi, all, I am planning to add clang-tidy checkers for my company. How to add a new module for my company? Please help, thanks in advance. I try to copy files from cert module, and rename cert to Misra, then add a rule named "m-0-1-1" by ./add_new_checker.py. then I run ninja check-clang-tool, but my case is failed due to below error Running ['clang-tidy',

My problem is that the .td and .h files are not shown as sources in the codeblocks (.cbp) output generated by cmake. I’m consuming the .cbp file with Qt Creator - it’s seems to be an otherwise excellent tool for llvm development. It seems that the culprit is llvm_process_sources function in cmake/modules/LLVMProcessSources.cmake. The addition of .td sources and header files is wrapped in the

On Oct 25, 2011, at 6:09 AM, Marcello Maggioni wrote: > Hi, I'm trying to compile the latest clang/llvm SVN versions and I get > this error on multiple systems : Linking, not compiling, but still. I am getting a similar error when building this morning. > Undefined symbols for architecture x86_64: > "clang::Sema::checkPseudoObjectRValue(clang::Expr*)", referenced

Hi, I'm trying to compile the latest clang/llvm SVN versions and I get this error on multiple systems : (Compiling with gcc): llvm[4]: Compiling cc1_main.cpp for Debug+Asserts build llvm[4]: Compiling cc1as_main.cpp for Debug+Asserts build llvm[4]: Compiling driver.cpp for Debug+Asserts build llvm[4]: Linking Debug+Asserts executable clang

On Thu, Aug 03, 2017 at 08:22:24AM -0600, Jonathan Roelofs wrote: > IIUC, you don't want to cross compile llvm itself (which is what those > instructions are for), but instead you want to *use* llvm to cross compile > things. > > To build your sysroot, you'll need to cross-build: > > 1) A libc. Good choices for that for baremetal are: newlib or musl. > 2)