Hello,
apart from the problem mentioned here: http://social.msdn.microsoft.com/forums/en-US/vssetup/thread/75057882-f2ff-49b9-9a7a-65f672f8e88f/
there are more problems with the .bat files.
I've first installed Visual C++ Express 2008, followed by the Windows SDK for Windows Server 2008. I did this to get the 64-bit compilers which don't ship with VCExpress. Now there's a file called vcvarsall.bat (in c:\program files (x86)\microsoft visual studio 9.0\vc).
To make it setup an environment for one of the 64-´bit compilers I am supposed to invoke it like
vcvarsall.bat amd64
or
vcvarsall.bat x86_amd64 (for the 32-bit to 64-bit cross-compiler)
However, this does not work. I've looked into the vcvarsall.bat file and it has pieces of code like this:
:x86_amd64
if not exist "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat" goto missing
call "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat"
The path is wrong! The location of vcvarsx86_amd64.bat is in \bin on my computer, not in \bin\x86_amd64 as suggested by the .bat file. Thus the 64-bit compilers are reported as "missing" even though they are present.
In conclusion, I can't do 64-bit command-line builds, because I use a build system which relies on calls like "vcvarsall.batx86_amd64" to set the proper environment variables.
Can you confirm this problem and/or suggest a fix?
Thanks for listening,
-Matthias