[Interest] 4NT shell and qmake

[Gisle Vanem]

I just installed QtCreator 3.0.3 along with the latest Qt 5.2.0 SDK using the
online installer. I loaded up one of the project in the QtCreator example-pane.
The YouTubeView project. I found that the bug I reported for Qt4 [1+2] involving 
nmake (or jom?) trying a "del non-existant-file" is still present in Qt 5. 

Here is the step where (the qmake generated) nmake is trying to add a 
manifest (edited lines for clarity):

  link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS 
  "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' 
  version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" 
  /MANIFEST /MANIFESTFILE:debug\youtubeview.exe.embed.manifest /OUT:debug\youtubeview.exe 
  @F:\TEMP\youtubeview.exe.8172.1718.jom
  if exist debug\youtubeview.exe_manifest.bak 
    fc /b debug\youtubeview.exe.embed.manifest debug\youtubeview.exe_manifest.bak >NUL || 
  del debug\youtubeview.exe_manifest.bak

  4NT: (Sys) Systemet finner ikke angitt fil.   <<<  ! error 2 = "File not found"  (ERROR_FILE_NOT_FOUND)

  "G:\Qt\5.2\5.2.0\mingw48_32\examples\webkitqml\build-youtubeview-Desktop_Qt_5_2_0_MSVC2010_32bit_
   OpenGL-  Debug\debug\youtubeview.exe_manifest.bak"

0 files deleted

jom: G:\Qt\5.2\5.2.0\mingw48_32\examples\webkitqml\build-youtubeview-Desktop_Qt_5_2_0_MSVC2010_32bit_OpenGL-Debug\Makefile.Debug 
[debug\youtubeview.exe] Error 2

jom: G:\Qt\5.2\5.2.0\mingw48_32\examples\webkitqml\build-youtubeview-Desktop_Qt_5_2_0_MSVC2010_32bit_OpenGL-Debug\Makefile [debug] 
Error 2

23:04:09: The process "G:\Qt\5.2\Tools\QtCreator\bin\jom.exe" exited with code 2.

-------------

Pushing the "Build project" once more, the project builds since now (it seems the .bak) file
is present.

I use 4NT 5.0 Unideo shell on Win-XP SP3. Please don't advice me to use the
inferior cmd shell :-)


[1] https://bugreports.qt-project.org/browse/QTBUG-29698
[2] http://lists.qt-project.org/pipermail/interest/2013-February/005990.html

  This bug-report of mine seems closed. But the bug is still there.

--gv