search for: llvm_export

...s and function, including clang::driver::Compilation. Now, since the export/import of classes/function is not supported by the LLVM+Clang project (incidentally, I really wish it was!), I had to modify the definition of the classes and functions that I need in order to have something like: class LLVM_EXPORT Compilation { . }; rather than class Compilation { . }; with LLVM_EXPORT being defined as: #ifdef _WIN32 #ifdef BUILD_LLVM #define LLVM_EXPORT __declspec(dllexport) #else #define LLVM_EXPORT __declspec(dllimport) #endif #else #define LLVM_EXPOR...

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:...

...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...

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

...ere is also the cost of maintaining a lists of export for the DLL, but hopefully we can use the llvm-echo to test it on the windows nodes so any failure to add new exports gets detected early. Now for the bike-shed questions, do we call it LLVM-c.dll or just LLVM.dll? Annotate all functions with a LLVM_EXPORT define or use a llvm-c.exports file? Thoughts and feedback welcome. Cheers, Jakob. [1] http://volt-lang.org [2] https://github.com/VoltLang/GenLLVMDLLPy/blob/master/GenLLVMDLL.py [3] https://github.com/Microsoft/LLVMSharp/blob/master/tools/GenLLVMDLL.ps1

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 useful even for...

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

...port for the DLL, but hopefully we can use > > the llvm-echo to test it on the windows nodes so any failure to add > > new exports gets detected early. > > > > Now for the bike-shed questions, do we call it LLVM-c.dll or just > > LLVM.dll? Annotate all functions with a LLVM_EXPORT define or use a > > llvm-c.exports file? > > > > Thoughts and feedback welcome. > > > > Cheers, Jakob. > > > > [1] http://volt-lang.org > > [2] https://github.com/VoltLang/GenLLVMDLLPy/blob/master/GenLLVMDLL.py > > [3] > https://github.com/Mi...

...t; >> > the llvm-echo to test it on the windows nodes so any failure to add > >> > new exports gets detected early. > >> > > >> > Now for the bike-shed questions, do we call it LLVM-c.dll or just > >> > LLVM.dll? Annotate all functions with a LLVM_EXPORT define or use a > >> > llvm-c.exports file? > >> > > >> > Thoughts and feedback welcome. > >> > > >> > Cheers, Jakob. > >> > > >> > [1] http://volt-lang.org > >> > [2] https://github.com/VoltLang/GenLLVM...

...nodes so any failure to > add > >>> >> > new exports gets detected early. > >>> >> > > >>> >> > Now for the bike-shed questions, do we call it LLVM-c.dll or just > >>> >> > LLVM.dll? Annotate all functions with a LLVM_EXPORT define or use > a > >>> >> > llvm-c.exports file? > >>> >> > > >>> >> > Thoughts and feedback welcome. > >>> >> > > >>> >> > Cheers, Jakob. > >>> >> > > >>> &...

...o test it on the windows nodes so any failure to add >>> >> > new exports gets detected early. >>> >> > >>> >> > Now for the bike-shed questions, do we call it LLVM-c.dll or just >>> >> > LLVM.dll? Annotate all functions with a LLVM_EXPORT define or use a >>> >> > llvm-c.exports file? >>> >> > >>> >> > Thoughts and feedback welcome. >>> >> > >>> >> > Cheers, Jakob. >>> >> > >>> >> > [1] http://volt-lang.org &g...

...to >> add >> >>> >> > new exports gets detected early. >> >>> >> > >> >>> >> > Now for the bike-shed questions, do we call it LLVM-c.dll or just >> >>> >> > LLVM.dll? Annotate all functions with a LLVM_EXPORT define or >> use a >> >>> >> > llvm-c.exports file? >> >>> >> > >> >>> >> > Thoughts and feedback welcome. >> >>> >> > >> >>> >> > Cheers, Jakob. >> >>> >&...