From kde-core-devel Sat Oct 02 19:06:34 2004 From: Antonio Larrosa =?utf-8?q?Jim=C3=A9nez?= Date: Sat, 02 Oct 2004 19:06:34 +0000 To: kde-core-devel Subject: Re: RFC: pkg-config for KDE Message-Id: <200410022106.39210.larrosa () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=109674400513714 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1170605.g8DLlYq9jT" --nextPart1170605.g8DLlYq9jT Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline El Wednesday 29 September 2004 19:27, Ian Reinhart Geiser escribi=C3=B3: > Example: > g++ someapp.cpp `pkg-config --cflags --libs kdeui` > vs > g++ someapp.cpp -I/some/hardcoded/path -L/some/other/hardcoded/path > -libkdeui -lkdecore > How would that handle configurations where people have different library=20 versions in different prefixes? Currently there's a kde-config, and you can= =20 have different kde-config binaries in different prefixes to choose which on= e=20 to use. Would we use a different directory to be included in=20 $PKG_CONFIG_PATH for each KDE/Qt installation ? Just in case I've not been clear enough. Currently, I have: antonio@tazend:~> pkg-config --libs qt-mt =2DL/usr/lib/qt3//lib -L/usr/X11R6/lib -L/usr/lib/ -L/usr/X11R6/lib/ -lqt-m= t=20 =2Dlpng -lz -lXi -lXrender -lXrandr -lXinerama -lXft -lfreetype -lfontconfi= g=20 =2DlXext -lX11 -lm -lSM -lICE -ldl -lpthread but I also have $QTDIR set to /usr/lib/qt3-head which is what is currently= =20 used to compile with the cvs version of Qt without having to use=20 =2D-with-qt-dir when running configure in kdelibs. Greetings, =2D- Antonio Larrosa Jimenez KDE developer - larrosa@kde.org http://developer.kde.org/~larrosa/ Search for beauty, it's the only thing which is worth in this nasty world. --nextPart1170605.g8DLlYq9jT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBXvw/3mWkZZAItZARAmapAJ4wmtTQI+34NN3AHWEuCUIgCIgBbQCgqLok TIQbHFCqpXm/awvapePKu8c= =g9Oy -----END PGP SIGNATURE----- --nextPart1170605.g8DLlYq9jT--