[Qt-interest] QT 4.4.3 compiling problem Window XP

[Oliver.Knoll at comit.ch]

Giancarlo Amati wrote on Wednesday, February 11, 2009 2:12 PM:

> .. I believe that although the INCLUDE and
> PATH variables have been set up with the path for Libraries and

PATH is only used when it comes to resolving the location of binary files (when calling them), so just make sure that it contains nmake etc.

The easiest way is to open a "Visual Studio Command Prompt" which usually also sets the proper INCLUDES (for the Visual Studio includes - but NOT necessarily the Microsoft platform SDK, if you have the Express version installed and a separate SDK installation!) and then add (don't overwrite!) the necessary INCLUDES (SDK, DirectX, ...).

And don't forget to also set the LIB (or LIBS) environment variable, which should point to all the necessary "lib" directories containing the *.lib files which are required for linking!

Also note that you only need to do this for _external_ libraries. Qt configure figures out its own includes/libs itself :)

> inlcude files, I think that nmake has problems with spaces in teh
> paths...because it's getting a nightmare here complining everything. 

I think there was another issue just recently on this list (or qt-creator at trolltech.com) with spaces in paths, in combination with qmake/nmake/(Qt Creator?).

The common sense was: don't put spaces in ANY path which is involved when compiling Qt (or any Qt/qmake based application) ;). The culprit is probably more on the side of qmake (or moc/uic), which doesn't properly (or not always) put ""s around paths. Because I don't think Visual Studio (nmake) itself has issues with spaces.

Anyway, don't use spaces ;) The "standard" location for Qt, for instance, seems to be e.g.

  c:\Qt\4.4.3\


Cheers, Oliver
-- 
Oliver Knoll
Dipl. Informatik-Ing. ETH
COMIT AG - ++41 79 520 95 22