On Wednesday 22 March 2006 10:24, Thiago Macieira wrote: > David Faure wrote: > >Apparently it's so that we can run things like > >qmake -query QT_INSTALL_HEADERS > > $ qmake -query QT_INSTALL_HEADERS > /home/tjmaciei/troll/qt-4.1-build/include > > $ pkg-config --variable includedir QtCore > /home/tjmaciei/troll/qt-4.1-build/include/QtCore > > $ pkg-config --cflags QtCore > -DQT_SHARED -I/home/tjmaciei/troll/qt-4.1-build/include > -I/home/tjmaciei/troll/qt-4.1-build/include/QtCore > > I can understand that it helps when pkg-config isn't installed, but I > believe that we will need pkg-config for other stuff too... So why not > use it, since it gives you more information?
For me it doesn't. $ qmake -query QT_INSTALL_HEADERS /devel/kde/src/4/qt-copy/include $ pkg-config --variable includedir QtCore $ pkg-config --cflags QtCore Package QtCore was not found in the pkg-config search path. Perhaps you should add the directory containing `QtCore.pc' to the PKG_CONFIG_PATH environment variable No package 'QtCore' found /devel/kde/src/4/qt-copy/lib/QtCore.pc exists, but I would have to modify PKG_CONFIG_PATH to see it. Setting PATH and LD_LIBRARY_PATH seems very natural to me, it's what anyone always does in order to use something that is in its own prefix. Setting PKG_CONFIG_PATH isn't so natural (especially since the variable is empty here, and should it really point to a lib directory...?) -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
