Alexander Neundorf wrote:
On Wednesday 09 April 2008, Andreas Pakulat wrote:
On 09.04.08 10:48:30, Mike Arthur wrote:
On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
Thats because qmake is in the PATH on unix usually, I think it works
autoamtically on windows too if the Qt/bin path is listed in the PATH
environment variable.
Is there any reason FindQT couldn't just look (by default) in the default
Qt Windows install location?
Probably, but having a quick look at FindQt.cmake that file is a
complete hack in itself, its underdocumented and you should probably use
It's a big file, mainly due to the fact that Qt has been split into many
modules, the structure in itself is quite ok.
The dependency detection near the end is a bit hacky (that's why I didn't
transfer that part (yet) to KDEs FindQt4.cmake).
Alex, I don't think FindQt4.cmake is what is being called a hack. It is
FindQt.cmake which tries to handle Qt3 or Qt4, and really is not very good.
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
