You have to setup environment variables BEFORE you run Creator. Otherwise Creator won't pick them up - that's how environment variables work. So open the command prompt, set your vars and then call Creator from the same command line. You can make a copy of qtenv.bat and modify the contents (remember to call Creator at the end).
Asperamanca (21st October 2009)
I have tried starting Creator from the QT command line before. I must have done something wrong then, because now it works!
qmake still crashes when I use the "Clean Environment", but works just fine with the regular environment (I have removed the Include references to Visual Studio 6 paths, and that seems to do wonders).
I'll now create my own bat file for starting Creator, as you suggested. THANKS!
It seemed a little daft to ask how to set environment variables from the command line when you already know how to set them from the command line by using qtenv.bat, hence my suggestion.
Also, as you probably know, environment variables set from the command line are lost when the command line is closed. Environment variables set from the GUI are kept across system reboots.
If you set the variables in the GUI, there's no need for a bat file, and you can start Creator from the desktop rather than from the command prompt.
I use Visual Studio 2008 with this configuration and I have no problems whatsoever - I just set QTDIR in the GUI environment variables page and everything works as it should.
I can't, because the global environment variables contain INCLUDEs that break QT. But I can just as well create a desktop link to my bat file - once I have that, there's really no difference to a "normal" link (except I have a command prompt open while running Creator - but I get that in 1.3.0 beta, anyway)
Visual Studio 6 is a different thing. I can't even blame it for having outdated header files.
Bookmarks