2024-08-05 20:04 AEST by Arthur Barrett - Currently we have several windows build environments:
+ acerw64lap / new-cvsnt-build-env for vs2003 cvs suite 2009/2010

+ evsprofile for vs2005 
* cvsflt2 (last compiled for ICON 6th August 2008)
* EVS (3.1.01) (user: T3\abarrett; or user: T3\Administrator)
* gsoap (user: T3\Administrator)
- wsdl2h
- soapcpp2
* SproutCore (propably user: T3\abarrett)

+ elmo3 for vs2005
* TortoiseShell (login as T3\abarrett)
* customer downloads SQL (login as T3\Administrator)
* WxWidgets 3.6.3

+ ??? for vs2008
* CVSNT 2.5.05


I want to combine these into one build environment, so I can build tortoiseact, tortoiseoverlays, wincvs and 
cvsnt plus all the suite components all together (with auto-generated build number).

This is going to be a pre-requisite to be able to then build everything for another environment like vs2022 see 
bug 7788

2024-08-05 20:09 AEST by Arthur Barrett - The main problem is the need to keep vs2005 and vs2003 installs separate.  

In the past whenever we've installed vs2005 it breaks vs2003.

I've narrowed this down to the fact that calling SetEnv.cmd uses VCDetect.exe to set the environment variable 
MSVCVer and the PATH to visual studio via VSVars32.bat

To 'fix' this I've changed SetEnv.cmd to use a new environment variable VCINIT:


REM -------------------------------------------------------------------
:DetectVC
REM -------------------------------------------------------------------
Echo.
Echo Attempting to detect a Microsoft Visual Studio installation
Echo.
rem CALL "C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\Tools\VSVars32.bat"
rem SET MSVCVer=7.1
IF NOT EXIST "%VCINIT%" goto DefVCEnv
Call "%VCINIT%"
Echo.
goto Chk_OS
:DefVCEnv
Call "%MSSDK%\Setup\VCDetect.exe" "%TEMP%\VCInit.bat"
IF NOT EXIST "%TEMP%\VCInit.bat" goto ErrorVCEnv
Call "%TEMP%\VCInit.bat"
Echo.
goto Chk_OS



you use it like this:


set VCINIT=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\VCInit2003.bat

call "C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\SetEnv.Cmd" /2000 /RETAIL


VCINIT has three options right now:
VCInit2003.bat
VCInit2005.bat
VCInit2008.bat