changes to how kdepimlibs and kdebase/workspace are installed and found

Brad King brad.king at
Tue Dec 9 17:38:33 CET 2008

Maciej Mrozowski wrote:
> On Tuesday 09 of December 2008 11:23:18 Modestas Vainius wrote:
>> Okay, but then I wouldn't mind e.g. /usr/lib/kde4/cmake or something
>> similar, just please do not pollute /usr/lib namespace directly. Likewise,
>> pkg-config has /usr/lib/pkgconfig.
> In my opinion /usr/lib/cmake/ would be fine to place those files - even 
> without creating subdirs inside like KdepimLibs and similar.

Many projects have a /usr/lib/<name>[-<version>] directory containing 
platform-specific data for the package.

Placement of the files near to the libraries in the installation is a 
*feature* of the find_package command.  It avoids all problems with 
multiple installations and multiple versions.  The command magically 
finds the files burried in the installation instead of in some central 
place which can have conflicts.  Furthermore, the relative path from the 
config files to the libraries remains fixed no matter where the package 
is installed.  This ensures that the locations reported by the file are 
correct with no special packaging or versioning work.


More information about the Kde-buildsystem mailing list