If in a .pro file, I use the following

Qt Code: 
  1. win32 { 
  2. 	debug {
  3. 		DESTDIR = ../build_win32/debug
  4. 	} else {
  5. 		DESTDIR = ../build_win32/release
  6. 	}
  7. }
To copy to clipboard, switch view to plain text mode 
Qt Creator will always look for the executable to run/debug in the ../build_win32/release directory, as if the "debug" scope was never active. The same happens removing the outer "win32 { ... }" condition or swapping the inner conditions and using "release" instead. I have tried "debug", "Debug", "DEBUG", "_DEBUG": none seems to be known to Qt Creator.

The build process in itself is correct (the executable ends up in the right directory), but launching the executable with F5, Qt Creator always looks for it in the 'else-d' directory and, of course, while attempting to debug, it finds nothing.

The same is true under Linux (of course replacing or removing the win32 condition!). I'm using Qt Creator 1.2.1 with Qt 4.5.2 32bit under XP SP3 or Ubuntu Jaunty.

Any suggestion would be appreciated.

M.

P.S.: I know that the "Shadow build" option would be a work-around, but I'm attempting to avoid using it as this setting cannot be set independently for each platform.