FindQt4.cmake

[Peter Kümmel]

Alexander Neundorf wrote:
> On Wednesday 01 February 2006 21:46, Brad King wrote:
>> David Faure wrote:
>>> 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?
>> How does bksys choose the include path for Qt?  I'm sure the logic is
>> not hard to implement in a CMake build system.
> 
> I just committed two modified FindQt4.cmake and FindKDE4.cmake.
> 
> FindQt4 now at first looks for include/QtCore/QtGlobal and after that 
> optionally for include/Qt/QtGlobal
> 
> Does this work for you on Windows and on OS X with Qt as a framework better ?
> 
> Bye
> Alex

There is an error in line 165 ${${...