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

[Dmitry Nezhevenko]

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.

-- 
WBR, Dmitry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://buildbot.net/pipermail/devel/attachments/20110921/61ea1360/attachment.bin>