6 Commits

Author	SHA1	Message	Date
Jeffrey Yasskin	6b718f73a5	Try r96559 for the third time. This time the shared library is only built if ... --enable-shared is passed to configure. llvm-svn: 97119	2010-02-25 06:34:33 +00:00
Jeffrey Yasskin	15983e57d6	Roll back r96959 again. ... llvm-svn: 96981	2010-02-23 20:53:37 +00:00
Jeffrey Yasskin	3ac46ccdff	Roll r96559 forward again, adding libLLVM-2.7svn.so to LLVM. This links 3 of ... the examples shared to make sure the shared library keeps working. llvm-svn: 96959	2010-02-23 18:10:07 +00:00
Jeffrey Yasskin	c451027db9	Roll back the shared library, r96559. It broke two darwins and arm, mysteriously. ... llvm-svn: 96569	2010-02-18 04:43:02 +00:00
Jeffrey Yasskin	f750fefaf8	Add a shared library for LLVM, named libLLVM2.7svn.(so|dylib), and add an ... --enable-shared configure flag to have the tools linked shared. (2.7svn is just $(LLVMVersion) so it'll change to "2.7" in the release.) Always link the example programs shared to test that the shared library keeps working. On my mac laptop, Debug libLLVM2.7svn.dylib is 39MB, and opt (for example) is 16M static vs 440K shared. Two things are less than ideal here: 1) The library doesn't include any version information. Since we expect to break the ABI with every release, this shouldn't be much of a problem. If we do release a compatible 2.7.1, we may be able to hack its library to work with binaries compiled against 2.7.0, or we can just ask them to recompile. I'm hoping to get a real packaging expert to look at this for the 2.8 release. 2) llvm-config doesn't yet have an option to print link options for the shared library. I'll add this as a subsequent patch. llvm-svn: 96559	2010-02-18 02:36:02 +00:00
Daniel Dunbar	0ab04bc27e	Switch to using 'lit.site.cfg.in' for the site config template for Unit tests, ... and generate it for CMake builds as well. llvm-svn: 86451	2009-11-08 09:07:51 +00:00