search for: llvm_build_llvm_c_dylib

We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option builds a shared object which exports the llvm-c interface but it only works on Darwin. tools/llvm-shlib/CMakeLists.txt is where how this is done is defined, and it looks like it does it by: * build LLVM.so * use nm+awk+sed to pick out the symbols starting with LLVM * build LLVM-C.s...

...ool from Visualstudio) and write all symbols with LLVM_ into a specific file 2017-04-05 20:40 GMT+02:00 Jakob Bornecrantz via llvm-dev < llvm-dev at lists.llvm.org>: > On Wed, Apr 5, 2017 at 5:20 PM, John Brawn <John.Brawn at arm.com> wrote: > > We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option > builds > > a shared object which exports the llvm-c interface but it only works on > > Darwin. > > > > tools/llvm-shlib/CMakeLists.txt is where how this is done is defined, > and it > > looks like it does it by: > > * build LLVM.so > >...

...gt;> > >> 2017-04-05 20:40 GMT+02:00 Jakob Bornecrantz via llvm-dev > >> <llvm-dev at lists.llvm.org>: > >>> > >>> On Wed, Apr 5, 2017 at 5:20 PM, John Brawn <John.Brawn at arm.com> wrote: > >>> > We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option > >>> > builds > >>> > a shared object which exports the llvm-c interface but it only works > on > >>> > Darwin. > >>> > > >>> > tools/llvm-shlib/CMakeLists.txt is where how this is done is > defined, >...

...>> file >> >> >> 2017-04-05 20:40 GMT+02:00 Jakob Bornecrantz via llvm-dev >> <llvm-dev at lists.llvm.org>: >>> >>> On Wed, Apr 5, 2017 at 5:20 PM, John Brawn <John.Brawn at arm.com> wrote: >>> > We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option >>> > builds >>> > a shared object which exports the llvm-c interface but it only works on >>> > Darwin. >>> > >>> > tools/llvm-shlib/CMakeLists.txt is where how this is done is defined, >>> > and it >>> &...

...7-04-05 20:40 GMT+02:00 Jakob Bornecrantz via llvm-dev >> >> <llvm-dev at lists.llvm.org>: >> >>> >> >>> On Wed, Apr 5, 2017 at 5:20 PM, John Brawn <John.Brawn at arm.com> >> wrote: >> >>> > We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option >> >>> > builds >> >>> > a shared object which exports the llvm-c interface but it only >> works on >> >>> > Darwin. >> >>> > >> >>> > tools/llvm-shlib/CMakeLists.txt is where how this is do...

Hello list! So I'm wondering if there is a will to ship a DLL with the C API exported? LLVM currently ships with LTO.dll which has some C api functions exported, made from the export file tools/lto/lto.exports, so it would not be the first DLL LLVM shipped. Currently I (and the users of my project[1]) are building it ourselves using this script[2] derived from the LLVMSharp script[3]. Which

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:

...ISel LLVM_BUILD_GLOBAL_ISEL:BOOL=ON //Build LLVM and tools with PGO instrumentation (experimental) LLVM_BUILD_INSTRUMENTED:BOOL=OFF //Build LLVM and tools with Code Coverage instrumentation (experimental) LLVM_BUILD_INSTRUMENTED_COVERAGE:BOOL=OFF //Build libllvm-c re-export library (Darwin Only) LLVM_BUILD_LLVM_C_DYLIB:BOOL=OFF //Build libllvm dynamic library LLVM_BUILD_LLVM_DYLIB:BOOL=OFF //Build the LLVM runtime libraries. LLVM_BUILD_RUNTIME:BOOL=ON //Build LLVM unit tests. If OFF, just generate build targets. LLVM_BUILD_TESTS:BOOL=OFF //Build the LLVM tools. If OFF, just generate build targets. LLVM_BUILD_...