introduce pkg-config files

[Andreas Pakulat]

On 25.10.10 20:21:43, Rolf Eike Beer wrote:
> Andreas Pakulat wrote:
> > On 25.10.10 12:56:25, Allen Winter wrote:
> > > On Monday 25 October 2010 12:29:42 pm Yury G. Kudryashov wrote:
> > > > Allen Winter wrote:
> > > > > Adding the KDE Buildsystem to this discussion..
> > > > > 
> > > > > My only concern is that pkg-config files are typically installed in
> > > > > locations (like /usr or /usr/local) where the regular user doesn't
> > > > > have write-access. Thereby causing problems when installing KDE as a
> > > > > regular user.
> > > > 
> > > > When you install an autotools package to /home/user/prefix, it installs
> > > > pkg- config files to /home/user/prefix/lib/pkgconfig. Then you need
> > > > export PKG_CONFIG_PATH to inform pkg-config about this location.
> > > 
> > > okey, good.
> > > then the kde pkg-config files would be installed in
> > > CMAKE_PREFIX_INSTALL/lib/pkgconfig, I guess.
> > > 
> > > cool.
> > > 
> > > then I can't think of any other objections.
> > 
> > The only thing I can think of is that it duplicates information at least
> > for kdepimlibs and kdebase. Those two modules already install the cmake
> > config files which (should) contain the same information. Wether or not
> > that is/should be blocking the addition of pc-files I don't know.
> 
> The easiest ways would be to simply drag in the pkg-config stuff using 
> pkg_check_modules from FindPkgConfig I guess.

Thats 'the other thing', i.e. use pkg-config files from cmake and we
already have pretty clear rules for that as Alex just answered. Whereas
as far as I understood the original mail is about generating and
installing .pc files from KDE libraries. That would allow projects that
don't want to use cmake (for whatever reasons) to use pkg-config to find
the kde libraries.

Andreas

-- 
You will be awarded a medal for disregarding safety in saving someone.