Please test: changes in how Qt4 is found
zack at kde.org
Fri Apr 28 18:07:17 BST 2006
On Thursday 27 April 2006 16:42, Michael Pyne wrote:
> On Thursday 27 April 2006 16:37, Benjamin Reed wrote:
> > On 4/27/06, Alexander Neundorf <neundorf at kde.org> wrote:
> > > Right now FindQt4.cmake in KDE svn is in sync with the one in cmake
> > > cvs. I don't want to fork it.
> > > So, cmake needs a FindQt4.cmake which just works on all supported
> > > systems without any additional unneccessary requirements. So relying
> > > only on pkg-config is no option.
> > > And I'm sure if I would change this today, by tomorrow my inbox would
> > > be flooded with emails "cmake doesn't find Qt4".
> > Then how about try pkg-config, and fall back if it's not found? That
> > will satisfy the people who rename things, and will still degrade
> > gracefully for pure-qt uses.
> If he *has* to do it one way anyways, why add the second method? If the
> second method doesn't add any functionality then it's just code that might
Yeah, I don't know what I was thinking. KDE using what pretty much every
single dependency we have is using on our main platform would be silly. It's
way better when we have our own stuff. Especially if instead just exporting
one environment variable to completely switch my build environments now I get
to remember what build system uses what to remember what exactly I need to
change to compile/link in a different environment. It's good because thanks
to that we'll all get to understand more build systems ;)
Individuals may be intelligent but holy shit are people stupid.
More information about the kde-core-devel