search for: llvm_include_tool

...b.freedesktop.org/mesa/mesa/blob/master/scons/llvm.py#L103 After reading https://llvm.org/devmtg/2015-04/slides/eurollvm-2015-build.pdf and https://llvm.org/docs/CMake.html I found these options to be relevant: LLVM_DYLIB_COMPONENTS, LLVM_BUILD_LLVM_DYLIB, LLVM_LINK_LLVM_DYLIB, LLVM_BUILD_TOOLS and LLVM_INCLUDE_TOOLS. Unfortunately LLVM_DYLIB_COMPONENTS depends on LLVM_BUILD_LLVM_DYLIB which doesn't support MSVC, I can turn off LLVM_BUILD_TOOLS and LLVM_INCLUDE_TOOLS if I figure out how to filter unneeded components as I would no longer need llvm-config anymore. -------------- next part -------------- An...

...ls svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk extra cd ../../../.. cd llvm/projects svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt cd ../.. mkdir build cd build export LLVM_TARGETS_TO_BUILD="ARM" export LLVM_BUILD_TOOLS==OFF export LLVM_INCLUDE_TOOLS=OFF export LLVM_BUILD_EXAMPLES=OFF export LLVM_INCLUDE_EXAMPLES=OFF export LLVM_BUILD_TESTS=OFF export LLVM_INCLUDE_TESTS=OFF I force it to build only for ARM, No test, No Examples and I ended up with In /build Clang=9MB (Crashed building Clang) lib=1.7GB Bin=2.5GB Main /llvm=531MB...

...ustin’s patch review feedback. In the build system today there is no strong distinction between ‘projects’ and ‘tools’. There are a few subtle differences, but I’m not sure any of them really matter. The differences are: (1) The projects directory is always configured, tools can be disabled using LLVM_INCLUDE_TOOLS=Off (projects and tools can both be individually disabled too) (2) Projects are configured before tools, so tools can rely on targets being created for projects (we don’t really use this, and anywhere we are is probably a bug) (3) Some projects have special handling. For example test-suite isn’t a...

...gt; >> In the build system today there is no strong distinction between ‘projects’ and ‘tools’. There are a few subtle differences, but I’m not sure any of them really matter. The differences are: >> >> (1) The projects directory is always configured, tools can be disabled using LLVM_INCLUDE_TOOLS=Off (projects and tools can both be individually disabled too) >> (2) Projects are configured before tools, so tools can rely on targets being created for projects (we don’t really use this, and anywhere we are is probably a bug) >> (3) Some projects have special handling. For example...

On 19 June 2015 at 15:57, Mehdi Amini <mehdi.amini at apple.com> wrote: > Hi, > > If you just want to *link* to LLVM, it is not clear to me why you are not > just relying on LLVM being built separately and have your project CMake > pointing to the llvm build directory and using llvm-config to populate the > linker argument? > > Best, > — > Mehdi > This is

...the build system today there is no strong distinction between ‘projects’ and ‘tools’. There are a few subtle differences, but I’m not sure any of them really matter. The differences are: >>>> >>>> (1) The projects directory is always configured, tools can be disabled using LLVM_INCLUDE_TOOLS=Off (projects and tools can both be individually disabled too) >>>> (2) Projects are configured before tools, so tools can rely on targets being created for projects (we don’t really use this, and anywhere we are is probably a bug) >>>> (3) Some projects have special handli...

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...CS:BOOL=ON //Generate build targets for the LLVM examples LLVM_INCLUDE_EXAMPLES:BOOL=ON //Include the Go bindings tests in test build targets. LLVM_INCLUDE_GO_TESTS:BOOL=OFF //Generate build targets for the LLVM unit tests. LLVM_INCLUDE_TESTS:BOOL=ON //Generate build targets for the LLVM tools. LLVM_INCLUDE_TOOLS:BOOL=ON //Generate build targets for the LLVM utils. LLVM_INCLUDE_UTILS:BOOL=ON //Doxygen-generated HTML documentation install directory LLVM_INSTALL_DOXYGEN_HTML_DIR:STRING=share/doc/llvm/doxygen-html //OCamldoc-generated HTML documentation install directory LLVM_INSTALL_OCAMLDOC_HTML_DIR:STRI...