From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-06-06 14:08:48
From: "Ralf W. Grosse-Kunstleve" <RWGK_at_[hidden]>
> > 2. It should be possible to configure the path to the compiler
> > so that users are not required to have the compiler in the path before
> > building. When builds use multiple toolsets it can be way too
> > try to prepare the environment for all of them simultaneously.
> On IRIX this is overkill, IMO. This platform is not like Linux or
> Windows. Multiple CC and cc installations are highly unlikely.
It's a matter of degree; you might install multiple versions, for example.
> On the
> other hand, the complexities of portably configuring system paths are
> difficult to handle (the old file did not work for me; I got very
> strange error messages having to do with system libraries not being
> I prefer approaches that deconvolute things.
> Wiring system paths into a
> build system goes in the opposite direction
I'm not suggesting any "wiring".
The rest of the toolsets work both ways: you can specify an installation
directory, or you can use the defaults that are already set up on your
> and makes the build system
> more complex than it should be, and much harder to get into for the
> novice. IMO setting up paths to a compiler should be done in the
> environment before the build system is called.
It's fine if you want to use the system that way, but there's no reason to
impose that on everyone else, nor to make the mipspro toolset different
from all the others in this respect.
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