Please test: changes in how Qt4 is found
kuba at mareimbrium.org
Fri Apr 28 17:52:35 BST 2006
On Thursday 27 April 2006 16:27, Alexander Neundorf wrote:
> On Thursday 27 April 2006 22:19, Benjamin Reed wrote:
> > On 4/27/06, William A. Hoffman <billlist at nycap.rr.com> wrote:
> > > >What platforms are those?
> > >
> > > Sun, HP, IRIX, Mac OSX, and even some linux systems.
> > dbus isn't on osx systems by default either, that's not going to stop
> > KDE from using it. There's already plenty of other non-apple-provided
> > stuff that's going to have to exist for kde apps to build, I don't see
> > why pkg-config should be any different. If it makes things easier in
> > the long run, I say go for it. Especially since a number of *other*
> > things KDE tests for need pkg-config *anyways*.
> Yes, but the FindQt4.cmake has to work also for non-KDE software. There is
> no reason to require pkg-config on a windows box in order to compile a Qt
> app. qmake does know from first-hand what is required to build a Qt app, so
> this is really the best way to find it out.
Couldn't agree more, especially that I'm migrating some more build stuff at
work to cmake. Cmake and Qt are the only dependencies for the product in
question, I'd consider it weird at least to add pkg-config to the mix if a
solution already exists and works.
More information about the kde-core-devel