search for: reexport_library

...on 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 I'm thinking that maybe we could make this not-darwin-specific by making use of utils/extract_symbols.py: * edit extract_symbols.py to add a --only_unmangled option (or maybe --only_prefix=LLVM or something like that) * on non-darwin use that instead of the existing command...

...orks 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 > > > > I'm thinking that maybe we could make this not-darwin-specific by making > > use of utils/extract_symbols.py: > > * edit extract_symbols.py to add a --only_unmangled option (or maybe > > --only_prefix=LLVM or something like that) > >...

...xt 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 > >>> > > >>> > I'm thinking that maybe we could make this not-darwin-specific by > >>> > making > >>> > use of utils/extract_symbols.py: > >>> > * edit extract_symbols.py to add a --only_unmangled option...

...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 >>> > >>> > I'm thinking that maybe we could make this not-darwin-specific by >>> > making >>> > use of utils/extract_symbols.py: >>> > * edit extract_symbols.py to add a --only_unmangled option (or maybe >>> &g...

...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 >> >>> > >> >>> > I'm thinking that maybe we could make this not-darwin-specific by >> >>> > making >> >>> > use of utils/extract_symbols.py: >> >>> > * edit extract_symbols.py to add a --on...

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