Build b41 & Microsoft Visual Studio.NET 2003 Professional Edition compiler
We have promoted build b41 today. Windows-i586 bundles were compiled with Microsoft Visual Studio.NET 2003 Professional Edition compiler (VS.NET 2003). So we have officially rolled over to VS.NET 2003 for our nightly windows-i586 build. Going forward we will be using VS.NET 2003 for our nightly build.
How to build mustang source using VS.NET 2003?.
The Microsoft Visual Studio.NET 2003 Professional Edition compiler can also be used for building the JDK 6.0. The compiler and other tools are expected to reside in the location defined by the variable VS71COMNTOOLS, which is set by the Microsoft Visual Studio.NET installer.
It is highly recommended that you run VCVARS32.BAT (usually found in C:\"Program Files"\"Microsoft Visual Studio .NET 2003"\Vc7\bin\VCVARS32.BAT) to set MSVCDIR, INCLUDE, LIB, and the PATH prior to building the JDK.
If your compiler resides in a place other than the default, you can set ALT_COMPILER_PATH to point to the location of the cl.exe compiler binary. If you are using MS VS.NET 2003 then you don't need to set ALT_MSDEVTOOLS_PATH variable. The compiler and tools binaries must be in the PATH.
We are also using the Platform SDK in Microsoft Visual Studio.NET 2003 for building the Java Plug-in and/or Java Web Start. This MSSDK is usually found in C:\"Program Files"\"Microsoft Visual Studio .NET 2003"\Vc7\PlatformSDK. If you are using VS.NET 2003 compiler for your build then you don't have to set ALT_DEPLOY_MSSDK.
Please let me know if you run into any issues.