FindQt4.cmake
Peter Kümmel
syntheticpp at gmx.net
Wed Feb 1 21:16:23 CET 2006
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>
>> Makes it on OS X really a difference to use #include <QtGlobal> with a additional
>> search path?
>
> Well, you could do that, but there's really no point as the Qt headers
> themselves
> use the <QtCore/QtGlobal> format internally so the command line switches to
> handle that *must* be passed to the compiler anyway just to compile on OSX.
> The "recommended way", as Ben put it, really is much cleaner and a better idea,
> imo.
>
> Cheers,
> Tanner
I also prefer the "recommended way", but then you have to change in every kdelibs
file the include commands.
Cheers,
Peter
More information about the Kde-buildsystem
mailing list