On Monday 17 April 2006 11:17, Stefan Gehn wrote: > Am Montag, 17. April 2006 04:10 schrieb Jon Keating: > > On Sun, Apr 16, 2006 at 11:47:09AM -0400, Mark Richards wrote: > > > debug this but I don't know much about Autoconf/automake so I was > > > wondering, maybe someone can explain why the KDE detection doesn't just > > > use > > > > > > kde-config --path lib > > > > > > to get the lib path? That seems to give the right answer on my systems > > > (FC4 > > > > Because when the KDE GUI was first made, it didn't exist I believe. > > I'll add support for it. > > kde-config is not meant to be used for that purpose, quoting a recent mail > > from David Faure on kde-devel: > > This isn't kde-config's purpose at all; kde-config is about > > KStandardDirs. > > > > On the other hand, I think the plan is to provide a pkg-config file, so > > you should be able to use pkg-config instead. > > Currently you have to rely on KDEDIRS, which is like the deprecated KDEDIR > but supports multiple paths. If KDEDIRS is not set at all you should at > least try: > > /usr > /usr/local/kde > > and maybe some distro-specific paths like: > > /opt/kde > /opt/kde3 > > Please don't abuse kde-config for detecting library paths, this specific > feature might go away as soon as kdelibs developers have added pkg-config > files.
I am not sure this is really necessary. It won't go away in KDE3 and KDE4 will need a new GUI plugin anyway. And since the Licq KDE GUI only needs kdelibs libraries it should work to just use kde-config --expandvars --install lib Cheers, Kevin -- Kevin Krammer <[EMAIL PROTECTED]> Qt/KDE Developer, Debian User Moderator: www.mrunix.de (German), www.qtcentre.org
pgpSlRBKq1dF0.pgp
Description: PGP signature
