From: Dan Gohman (gohmandj_at_[hidden])
Date: 2002-06-07 17:48:06
On Thu, Jun 06, 2002 at 11:40:44AM -0700, Ralf W. Grosse-Kunstleve wrote:
> On IRIX this is overkill, IMO. This platform is not like Linux or
> Windows. Multiple CC and cc installations are highly unlikely. 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 would disagree. The `modules' mechanism makes multiple versions of
various packages, including MIPSpro, quite possible.
The file I'm preparing to submit has completely reorganized logic
for this. Perhaps it will work better for you.
> I prefer approaches that deconvolute things. Wiring system paths into a
> build system goes in the opposite direction 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. This can easily be
> achieved with simple shell scripts or batch files.
Forcing the user to use the default library paths, however simple it
may be, is too limiting for at least my needs. The project I'm on right
now requires the ability to specify alternate paths, so I won't be
able to use such a system.
-- Dan Gohman gohmandj_at_[hidden]
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