[Buildbot-devel] BuildBot & Visual Studios....

[BRM]

----- Original Message -----

> From: Dmitry Nezhevenko <dion at dion.org.ua>
> To: "buildbot-devel at lists.sourceforge.net" <buildbot-devel at lists.sourceforge.net>
> Cc: 
> Sent: Wednesday, September 21, 2011 3:56 PM
> Subject: Re: [Buildbot-devel] BuildBot & Visual Studios....
> 
> On Wed, Sep 21, 2011 at 10:37:21AM -0700, BRM wrote:
>>  > Actually no. There is nothing special to configure on slave. Just 
> install
>>  > as many VS versions as you need.
>>  > 
>>  > I'm using VSxxCOMNTOOLS environment variable to calculate path to 
> visual
>>  > studio compiler. It's added by VS installer. So on master you 
> should just
>>  > choose which MSVC version to use for particular builder.
>>  > 
>>  > So:
>>  >     addStep(MSVC(commToolsName = "VS90COMNTOOLS", ...)) -- 
> for VS2008
>>  >     addStep(MSVC(commToolsName = "VS71COMNTOOLS", ...)) -- 
> for VS2003
>>  > 
>>  > As I said, this don't require any manual changes on slave. Just 
> unpatched
>>  > slave. Environment variables will be added by MSVC installer
>> 
>>  Environment variables are not necessarily a good thing to rely on.
>>  I did load up my Virtual Machine (which has VS6, VS2003, VS2008, and VS2010 
> installed) to take a look, and I can see what you mean.
>>  However, VS6 doesn't provide such a variable, and while I do realize 
> that usage of VS6 is far lower than any other it's still a formidable force.
>>  So a way that it useful on all systems, for all versions in use is probably 
> best.
>> 
> 
> You are right. VC6 doesn't have this. But VC6 also don't have vcbuild
> IIRC. And finally it's just a piece crap...
> 
> I still remember hacks like "#define for if (false); else for" to let 
> it
> compile somethings. boost already dropped VC6 support.

That may be. But there are still those of us who are stuck with it for various reasons - especially in the commercial world.
So supporting it is still a good thing, especially when the support is so cheap to do. ;-)

Ben