Keeping binary compatibility
faure at kde.org
Mon Oct 4 13:06:31 BST 2010
On Monday 04 October 2010, David Jarvie wrote:
> On Fri, October 1, 2010 2:32 pm, Lubos Lunak wrote:
> > Therefore I propose the following:
> > - private libraries do not (obviously ...?) install their .h files and do
> > use
> > NAMELINK_SKIP option in install (see e.g.
> > http://websvn.kde.org/trunk/KDE/kdebase/workspace/khotkeys/libkhotkeyspri
> > vate/CMakeLists.txt?r1=862343&r2=895764)
> Could you please explain why using NAMELINK_SKIP is better for private
> libraries? What difference does it make whether links to the shared
> library file are created?
I think this is because:
* foo.so.4 is used at runtime, so it needs to be installed
* foo.so is used at link time, so it does not need to be installed for private
/me adds NAMELINK_SKIP to libkonquerorprivate.
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).
More information about the kde-core-devel