Qt Compile Error in Vista/VS2008
-
Hello!
I´m having some dificulties to compile the qt 4.6.3 in Windows Vista/VS2008.
I configured the make with -no-webkit -no-qt3support -no-scripttools -no-script and after hours compiling, this occours:Microsoft (R) 32b/64b MIDL Compiler Version 7.00.0500
Copyright (c) Microsoft Corporation 1991-2006. All rights reserved.
Processing C:\Qt\2010.04\qt\tools\activeqt\testcon\testcon.idl
testcon.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\ocidl.i
dl
ocidl.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\oleidl.
idl
oleidl.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\objidl.
idl
objidl.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\unknwn.
idl
unknwn.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\wtypes.
idl
wtypes.idl
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\basetsd
.h
basetsd.h
Processing C:\Arquivos de programas\Microsoft SDKs\Windows\v6.0A\Include\guiddef
.h
guiddef.hmidl : error MIDL9008 : internal compiler problem - See documentation for sugges
tions on how to find a workaround.
midl: Assertion failed: ( rc < _MAX_DIR ) && ( rc != 0 ), file d:\longhorn\com\r
pc\midl\front\filehndl.cxx, line 821
NMAKE : fatal error U1077: 'midl' : return code '0x2330'
Stop.
NMAKE : fatal error U1077: '"c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN
\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.This is weird, because I don´t have any folder named longhorn in drive D (I´m compiling in Drive C).
What can I do to fix this?
Thanks in advance
Best Regards,
Marcelo M. Paz
-
marcelopaz Have you updated your Visual Studio with all the latest updates? Especially SP1?
I have found this "thread":http://social.msdn.microsoft.com/forums/en-US/vclanguage/thread/5abc3918-af6e-40e4-9962-40d90edefb1e that is about your issue however I suggest to check for updates using Microsoft Update.