> I'm a newbie about llvm. Now, our project need the dynamic link library(dll)
> about all of llvm library, such as libLLVMCore.dll, libLLVMSupport.dll, and
> so on. How should I do?
You may do, "/path/to/configure --enable-shared=yes",
to build LLVM-2.8svn.dll.
On your project, you have to specify to linker,
"-L/path/to/dll -lLLVM-2.8svn"
(maybe with -Wl,--enable-auto-import)
We provide not individual DLLs but a "BIG" one.
We don't provide import libraries.
I think "DLL" feature is still experimental, and I need more feedback.
When you met any troubles with DLL, ask here or file bugs!
Have fun!
...Takumi
_______________________________________________
LLVM Developers mailing list
LLV...@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Excuse me, I gave up Debug build earlier due to my poor hosts.
I will improve able to build Debug ;)
You may build with --enable-optimized=yes
(or, make ENABLE_OPTIMIZED=1)
btw, DLL builder has implemented since Aug.
It might be easier to port DLL stuff to 2.6 :) Do you try?
...Takumi
2010年9月2日 17:16:25 UTC+9 yuan zheng <tsinghu...@gmail.com>:
I am also interesting on llvm with MingW.
I do not understand why "easier" for build DLL on llvm-2.6. Is there
any one who can build dll library of llvm-2.6 in MingW development
environment?
Thanks
MK
> I am also interesting on llvm with MingW.
> I do not understand why "easier" for build DLL on llvm-2.6. Is there
> any one who can build dll library of llvm-2.6 in MingW development
> environment?
Maybe this helps:
http://article.gmane.org/gmane.comp.compilers.llvm.devel/10660/
LLVM changed a bit since I wrote that post and some files no longer
exists (the standalone .o files that acted as libraries, for instance)
but the procedure consisting on extracting all object files from the
static libraries and relink them into a single dll should still apply.