Displaying 3 results from an estimated 3 matches for "libllvmfoobar".
2016 Jan 19
2
Problem with the way BUILD_SHARED_LIBS=ON handled in llvm 3.8
...<beanz at apple.com> wrote:
> The LLVM libraries are not API stable (especially not the ones you generate with BUILD_SHARED_LIBS). Those libraries are really not intended to ship.
I know that's why I need them versioned. Currently we (openSUSE) ship
libLLVM package which will install libLLVMFooBar.so.3.7 files and
llvm-devel package will ship unversioned libLLVMFooBar.so.
So, any application linking against LLVM generates a dependency
against the versioned libLLVMFooBar.so.3.7 and not against the
unversioned library. This way when we ship the new libLLVM 3.8 old
application will have to be...
2016 Jan 18
2
Problem with the way BUILD_SHARED_LIBS=ON handled in llvm 3.8
Hi,
For lllvm 3.7 and before BUILD_SHARED_LIBS=ON would produce versioned
shared libs like
libLLVMLTO.so (symlink)
libLLVMLTO.so.3.7 (symlink)
libLLVMLTO.so.3.7.0 (real file)
now it just builds an unversioned libLLVMLTO.so file which I believe
is a problem because when a program links to llvm it generates a
runtime dependency on libLLVMLTO.so instead of libLLVMLTO.so.3.7.0
which will break
2016 Jan 26
2
Problem with the way BUILD_SHARED_LIBS=ON handled in llvm 3.8
...ork) rather than fixing BUILD_SHARED_LIBS which was never intended to work for this use case.
>
> Either way, patches welcome.
This seems to be due to your commit http://reviews.llvm.org/D13841 ,
the problem is I don't get properly versioned symlinks even after
install. All I get is bare libLLVMFooBar.so files.