[CMake] Re: FindQt4 in 2.4.8 bug
Fernando Cacciola
fernando.cacciola at gmail.com
Fri Jan 25 13:58:54 EST 2008
clinton at elemtech.com wrote:
> On Friday 25 January 2008 10:58:19 am Fernando Cacciola wrote:
>> Hi,
>>
>> I've been using 2.4.7 until this morning when I saw the 2.4.8
>> announcement
>> and jumped right away to install it (silly me).
>> I have some script that finds Qt4 but stopped working on 2.4.8.
>> Tracing the problem in FindQt4.cmake I found this...
>> There is one (at least one) SET command like this:
>> SET( QT_INCLUDE_DIR ${qt4_include_dir} CACHE PATH "")
>> which fails to actually set the value of QT_INCLUDE_DIR
>> It works fine if DOCSTRING is prepended in front of "":
>> SET( QT_INCLUDE_DIR ${qt4_include_dir} CACHE PATH DOCSTRING "")
>> Is this a bug in FindQt4.cmake? ( was this differently in 2.4.7? )
>> A bug in 2.4.8 ( DOCSTRING should not be needed? )
>> A feature in 2.4.8 ? (is needed just now? )
>>
>
> Or perhaps ${qt4_include_dir} is empty
No, is not.
It contains the correctm path.
As I said, if I append the DOCSTRING, QT_INCLUDE_DIR is also set to the
correct values.
I know because I printed the values of all the involved variables (from the
file beginning actually, otherwise I would have never located the problem
exactly there)
I ommitted the details on how I concuded this because I wasted enough time
finding the problem, now I can't waste even more time showing that I did not
make any silly mistake like that.
>, so it messes up the rest of the
> arguments.
> This is on a Mac, right?
>
No, is Vista.
> And is Qt configured with -no-framework?
> Did it set QT_QTCORE_INCLUDE_DIR
Yes
>and QT_LIBRARY_DIR correctly?
>
Don't know and I don't care since this is defined after that.
Fernandi
More information about the CMake
mailing list