msvcrt71d.dll is *not* from msvc2005 but from msvc2003.net (msvc2005 has msvcrt80d.dll)
You build your moc.exe with msvc2003.net in debug mode (don't know how you did this). Rebuild your qt-lib with msvc2005 and it should work fine.
msvcrt71d.dll is *not* from msvc2005 but from msvc2003.net (msvc2005 has msvcrt80d.dll)
You build your moc.exe with msvc2003.net in debug mode (don't know how you did this). Rebuild your qt-lib with msvc2005 and it should work fine.
skaiser (24th March 2006)
My pardons.
Thanks Christian for a mighty helpful post! Man the light bulbs came on.
I never built moc.exe-- it came with the Qt installation. So now things are clearer-- Trolltech's qt-win-commercial-4.1.1 installer comes with pre-built binaries, and Trolltech built them with .NET 2003 in debug mode.
This makes sense, since the installer file is named "qt-win-commercial-4.1.1-vs2003.exe". heheh. As a newbie, I failed to recognize the subtle difference and what that meant for VS 2005.
Also, one installer doc does say that I am supposed to configure and build the package first with nmake. So as you suggest, I guess I should figure out how to do that and see what happens.
Thanks Brandybuck for chiming in. I have considered the Open Source version, but I'm very keen to get the VisualStudio integration thing happening. If it doesn't work right, then I'll drop back to the Open Source and probably try a KDE / KDevelop environment. Got a big project ahead and want to get the best tools I can up front here before settling in.
Steve
Bookmarks