MSVC debug dll's pulled in by release version of Qtilities

[Simon Gemmell]

I don't know that this is a problem with Qtilities or qmake or how I'm running things, but essentially I build Qtilties using this batch script:

copy /Y Qtilities\src\Dependencies.pri Dependencies.pri.bak

copy /Y Qtilities\src\Qtilities.pri Qtilities.pri.bak

python FindReplaceInFile.py Qtilities\src\Dependencies.pri "^\s*(DEFINES\s*\+=\s*QTILITIES_PROPERTY_BROWSER)" "#\g<1>"

python FindReplaceInFile.py Qtilities\src\Qtilities.pri "^#\s*(DEFINES\s*\+=\s*QTILITIES_NO_HELP)" "\g<1>"

pushd Qtilities\src

nmake distclean

qmake

nmake Debug

nmake Release

popd

move /Y Dependencies.pri.bak Qtilities\src\Dependencies.pri

move /Y Qtilities.pri.bak Qtilities\src\Qtilities.pri

REM Put the dll's in a folder that the executable will look for them - either running the exe directly or through VS.

xcopy /Y Qtilities\bin\*.dll ICDE\Binaries\

xcopy /Y Qtilities\bin\*.dll ICDE\Build\ICDEApplication\

When I build my installer and install and then run my exe QTILITIESCOREGUI-1.2.DLL pulls in MSVCP100D.DLL (i.e. the Debug one). Screenshot of depends.exe attached. 

After some fiddling around I worked out that if I just grab Qtilities and build in Release mode only (via nmake Release) it's fine and pulls in the non-debug version. But if I build in Debug and then Release we bring in the Debug version (even though we're using the release version of the qtilities dll in both cases). So I don't know where the problem resides, maybe I should be doing an nmake clean between Debug and Release? But that doesn't seem right.... maybe it's a problem with visual studio itself.... I do note that in the makefile it's debug and release (as opposed to Debug and Release) but it runs so I assume it's finding those targets OK... 

[Simon Gemmell]

nmake debug

nmake clean

nmake release

And it correctly pulls in the non-debug visual studio dlls