Channel Mike

I've recently been trying to build some open source code that uses the QT libraries from Trolltech/Nokia on Windows. I haven't done any development for a while, so I removed all of the old SDKs and IDEs from my machine and started fresh with Visual C++ 2010 Express Edition. I then downloaded QT 4.6.3 and ran the Windows Installer. Their Visual Studio integration package does not work with Express editions, so I bypassed it. I then followed the instructions to install the QT libs to my environment for building.
After running the "configure" in the Visual Studio Command Prompt, I ran "nmake" in the same command session. This is where I ran into slight problems.
After repetitive errors from:
...\VC\INCLUDE\utility(163), and
...\VC\INCLUDE\utility(166), and
...\VC\INCLUDE\utility(167), and
...\VC\INCLUDE\utility(247),
concerning file:
...\QT\4.6.3\src\3rdparty\javascriptcore\JavaScriptCore\runtime\StructureTransitionTable.h(146), and
...\QT\4.6.3\src\3rdparty\javascriptcore\JavaScriptCore\runtime\StructureTransitionTable.h(153),
it appears that Microsoft has made their compiler, cl.exe, pickier than it used to be about null pointers. There are two lines that pass a 0 value to a function/template expecting a pointer. This used to work without problem, but no longer does. Explicitly casting the 0 as a pointer fixes the problem and keeps the compiler happy.

From:

146: table()->add(key, Transition(structure, 0));
153: table()->add(key, Transition(0, structure));


To:

146: table()->add(key, Transition(structure, (QTJSC::Structure *)0));
153: table()->add(key, Transition((QTJSC::Structure *)0, structure));


And the compiler is off and running through the rest of the code.