summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-shlib
Commit message (Collapse)AuthorAgeFilesLines
...
* Roll back r96959 again.Jeffrey Yasskin2010-02-231-67/+0
| | | | llvm-svn: 96981
* Oops. Pass -lgcc _only_ on ARM, not on everything except ARM.Jeffrey Yasskin2010-02-231-1/+1
| | | | llvm-svn: 96965
* Roll r96559 forward again, adding libLLVM-2.7svn.so to LLVM. This links 3 ofJeffrey Yasskin2010-02-231-0/+67
| | | | | | the examples shared to make sure the shared library keeps working. llvm-svn: 96959
* Roll back the shared library, r96559. It broke two darwins and arm, ↵Jeffrey Yasskin2010-02-181-61/+0
| | | | | | mysteriously. llvm-svn: 96569
* Add a shared library for LLVM, named libLLVM2.7svn.(so|dylib), and add anJeffrey Yasskin2010-02-181-0/+61
--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
OpenPOWER on IntegriCloud