FindQt4.cmake

[David Faure]

On Wednesday 01 February 2006 21:16, Peter Kümmel wrote:
> Tanner Lovelace wrote:
> > On 2/1/06, Peter Kümmel <syntheticpp at gmx.net> wrote:
> >> I suggest forcing to #include <Qt.../Q...> will break a huge amount of code.
> > 
> > Why do you say that?
> > 
> 
> Look into a arbitrary kdelibs file and you don't see any directories in the includes.
> ATM it's a mixture of #include <QClass> and #include <qclass.h>

Yeah, and I think it would be a *major* PITA to have to write #include <QtCore/QString.h>.
In fact I would prefer a solution that forbids it...

One of the reasons is that #include <QString> can be automated by the editor, 
when pressing a key shortcut while the cursor is on QString. If we need to
add QtCore in front, we need a huge map or some qt-directory-looking code....

The other reason is simply that it works with other buildsystems. A buildsystem 
should compile the code that other buildsystems (e.g. Qt or unsermake) can compile, 
not mandate that the code be changed first.

Surely there's another solution for Mac OSX, given that it works in bksys?

> Sounds like the perfect chore for a perl or python script. :-)
Veto.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).