search for: llvm_exports

Displaying 12 results from an estimated 12 matches for "llvm_exports".

Did you mean: llvm_export
2015 Mar 10
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Ok, I have just found the cause of the error messages I am getting, and it now makes sense to me why the 'normal' build works fine on Windows, Linux and OS X, and why my personal build works on Linux and OS X, but not on Windows. However, I still don't understand why I am getting the error messages I am getting. Anyway, it has to do with wanting to export some classes and function,
2013 May 08
0
[LLVMdev] Shared library support of llvm
Actually, adding a LLVM_EXPORT macro would be positive for other environments, because you can then build LLVM as a shared library with -fvisibility=hidden and use LLVM_EXPORT to only make public symbols visible. There are several advantages to this, as noted here: http://gcc.gnu.org/wiki/Visibility From: Reid Kleckner Sent: Wednesday, May 08, 2013 6:21 PM To: Peng Cheng Cc: LLVMdev at
2011 Apr 25
0
[LLVMdev] Big Windows Clang DLL
...ll path strings in a new target property. 4. Add a new "add_clang_dll" cmake macro for creating the big DLL. This macro operates like "add_clang_library", but always builds a DLL target, and doesn't collect the source paths. It also passes "LLVM_USE_DLL" and "LLVM_EXPORTS" defines to the compiler, to enable the symbol exports to be described later. 5. Create a new "ClangDLL" project under tools/clang/lib for creating the big DLL, which uses the new "add_clang_dll" macro. 6. Add new "set_clang_components" and "set_clang_llvm_...
2013 May 08
5
[LLVMdev] Shared library support of llvm
According to http://llvm.org/docs/CMake.html, "Shared libraries are not supported on Windows and not recommended in the other OSes". The problem is that static libraries have some limitations, especially when linked into multiple shared libraries, the global data of llvm could have multiple copies leading to undefined behaviors. This has caused much pains during my usage of llvm. My
2017 Mar 30
2
Shipping LLVM.dll for the C API with the Windows installer.
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
2013 May 08
1
[LLVMdev] Shared library support of llvm
On Wed, May 8, 2013 at 8:55 PM, Morten Ofstad <morten at hue.no> wrote: > Actually, adding a LLVM_EXPORT macro would be positive for other > environments, because you can then build LLVM > as a shared library with -fvisibility=hidden and use LLVM_EXPORT to only > make public symbols visible. There are several > advantages to this, as noted here: > I agree, this would be
2008 May 14
1
[LLVMdev] LLVM as a DLL
Owen Anderson <resistor at mac.com> writes: > On May 13, 2008, at 6:38 PM, Óscar Fuentes wrote: >> Last time I checked, building LLVM on Windows (MinGW or MSVC) did not >> produce dlls. >> >> Has this changed? >> >> I was succesful converting the libraries produced by MinGW to dlls, >> though. > > It's a little bit immaterial whether
2017 Apr 05
2
Shipping LLVM.dll for the C API with the Windows installer.
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
2017 Apr 06
2
Shipping LLVM.dll for the C API with the Windows installer.
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
2017 Jul 10
2
Shipping LLVM.dll for the C API with the Windows installer.
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
2017 Jul 06
0
Shipping LLVM.dll for the C API with the Windows installer.
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. > >
2017 Jul 10
0
Shipping LLVM.dll for the C API with the Windows installer.
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