On Wednesday 05 April 2006 17:57, William A. Hoffman wrote: > At 11:04 AM 4/5/2006, Simon Hausmann wrote: > >On Wednesday 05 April 2006 16:49, William A. Hoffman wrote: > >> At 10:37 AM 4/5/2006, Simon Hausmann wrote: > >> >We solved it differently now. After some discussion and thinking we > >> > decided against putting it into qmake. Instead we store the path to > >> > uic and moc now in the pkgconfig files. > >> > > >> >That means with Qt 4.2 you'll be able to use pkg-config to figure out > >> > the libraries + paths for building a Qt application as well as the > >> > path to moc/uic. > >> > > >> >For example: > >> > > >> >pkg-config --variable=moc_location QtCore > >> > >> What about systems that do not have pkg-config? > > > >For those you have to assume the fallback of a in-place installation where > >everything is inside $prefix and the binaries aren't renamed. This in > >particular includes Windows :) > > I don't think it is just windows, and also this does make it harder to > work with a non-installed qt, unless the user sets PKG_CONFIG_PATH and > some other stuff, pkg-config will not even know about the users local > qt installation.
Yes, I agree. Before I joined this mailing list here, I didn't even know that an environment variable PKG_CONFIG_PATH exists. So I would not have guessed what might be going wrong. I actually liked the option to query qmake for information. Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org - http://www.kde.org alex AT neundorf.net - http://www.neundorf.net _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
