From: Ali Azarbayejani (ali_at_[hidden])
Date: 2003-05-08 14:26:07
David Abrahams wrote:
> > Also, I don't want my build to produce side effects.
> What side-effects? Environment settings for each invoked action
> disappear as soon as the action completes.
If that's true, then there are no side effects and I'm happy. I thought
that vcvars32.bat set my Windows Environment, and was permanent. If
you're only setting shell environment, that's fine.
> > How about
> > (1) check default installation locations; if so, use those
> > (2) check if tools (cl, link) are in PATH; if so, use those
> I think you got those backwards. If the user doesn't specify a
> version to use, IMO you should use the one in his path (if any).
> Users expect to be able to invoke the vcvars32.bat for a particular
> compiler version and then invoke a build to get it to use that
> > (3) NEVER invoke vcvars32.bat if it's going to make a permanent change
> > to my Environment;
> It is NEVER going to make a permanent change to your environment.
ok. that's what i want.
> > at least I need the option to be able to invoke a
> > completely non-intrusive build with no side effects.
> You already do.
> > (4) Documenting and warning about vcvars32.bat are fine and good, and if
> > a user wants to invoke it manually, it should make (2) work, but don't
> > do it for me automatically unless it can be done in a way that doesn't
> > produce side effects.
> It's basically impossible to produce any side effects, so you don't
> have anything to worry about.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk