[Qt-interest] qmake, nmake and Windows 7

Sven Grunewaldt strayer at olle-orks.org
Tue Jan 20 11:21:00 CET 2009


I'm currently testing the Windows 7 Beta and I'm facing a problem with
Qt and Visual Studio 2008.

It seems that qmake in combination with nmake is broken while creating a
vcproj and compiling WITHIN VS works fine.

The error appears after the linker:
-------------------------------------------------------------------------------
link /LIBPATH:"e:\Entwicklung\lib\qt-4.4.3\lib" /LIBPATH:"e:\Entwicklung
\lib\qt-4.4.3\lib" /NOLOGO /INCREMENTAL:NO /MANIFEST
/MANIFESTFILE:"tmp\obj\rele
ase_shared\t1.intermediate.manifest" /SUBSYSTEM:WINDOWS
"/MANIFESTDEPENDENCY:typ
e='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0'
publicKeyTo
ken='6595b64144ccf1df' language='*' processorArchitecture='*'"
/OUT:release\t1.e
xe @C:\Users\Strayer\AppData\Local\Temp\nmC6FD.tmp
        mt.exe -nologo -manifest
"tmp\obj\release_shared\t1.intermediate.manifes
t" -outputresource:release\t1.exe;1

mt.exe : general error c101008d: Failed to write the updated manifest to
the res
ource of file "release\t1.exe". The binary is not a valid Windows image.
NMAKE : fatal error U1077: ""C:\Program Files\Microsoft
SDKs\Windows\v6.0A\bin\m
t.exe"": Rückgabe-Code "0x1f"
Stop.
NMAKE : fatal error U1077: ""C:\Program Files\Microsoft Visual Studio
9.0\VC\BIN
\nmake.exe"": Rückgabe-Code "0x2"
Stop.
-------------------------------------------------------------------------------

I know that Windows 7 is still a beta OS but maybe we can figure out
what the problem is... Somehow either the linker or a process before
renders the executable useless.
As I mentioned above compiling the same example (tutorial/t1) within VS
by doing "qmake -tp vc" works fine.

Generated Makefile: http://pastebin.ca/1310920
Generated Makefile.Debug: http://pastebin.ca/1310922



More information about the Qt-interest-old mailing list