search for: reexport_librari

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.so using a -reexport_library linker option

The following is an older commandline i used. Have a more recent one at home. But basically you can write it as batch and trigger it within a target during the build(never got targets into correct order, i am a cmake noob) So for reference, i'll post this one and look for the recent one at home(if that didn't go down with my recent hdd crash): cmd /Q /V:ON /c "for /F

Thanks for starting! Btw here is my CMD version: cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set symbolname=%e & echo !symbolname:~1!))" You run it in the directory with all the llvm*.lib (yes the ThinLTO is excluded in this example but can

Made a bit of headway here: https://reviews.llvm.org/D35077 Cheers, Jakob. On Thu, Apr 6, 2017 at 2:34 PM, Alexander Benikowski <sebal007 at googlemail.com> wrote: > Maybe someone can use this as a startingpoint to add the windows-specific > commandblock which is triggered instead of the Darwin one together with a > proper setup of targets to have the libs build before. > >

I am sorry, just noticed i repeated myself :( 2017-07-10 15:20 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>: > Thanks for starting! > Btw here is my CMD version: > > cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F > "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') 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

Hi all, I've been thinking about how best to represent MachO's LC_REEXPORT_DYLIB (used even by libSystem.dylib to provide its various sub-components[*]). It looks like this functionality would naturally fall into the InputGraph, in analogy with Groups and Archives. Unfortunately, it's rather more dynamic than the existing cases: we don't know the needed files before parsing the