You are not logged in.
Hi
I'm preparing a package for my application.
The application is divided on some executables and three shared libraries for them (not for the whole system).
But only main application should be "visible" for end user in /usr/bin.
Natural way seems to be to put those libraries and binary files into /usr/lib/myapp.
So I found how to use rpath for this approach and it works under Arch Linux.
Unfortunately other Linux-es (deb based, rpm based) are more restricted and they will complains about using rpath.
To put those libs just in system wide /usr/lib may work but it requires proper soname and versioning the libraries and probably makes mess in /usr/lib. This app no needs that.
Also LD_LIBRARY_PATH is not good solution for system package.
Is there some best way or just common way tu put proper path of /usr/lib/myapp to executable during installation process or during package building?
Last edited by SeeLook (2015-02-03 11:40:29)
Offline
Sorry for troubles...
The rpath method is the best in this case (libraries are used only by particular application end they are placed inside /usr/lib/package).
I had wrongly set rules of cmake, here is some doc how to do it properly:
http://www.cmake.org/Wiki/CMake_RPATH_handling
Last edited by SeeLook (2015-02-03 11:41:18)
Offline