From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-06-06 14:12:18
On 2002-06-06 at 11:40 AM, RWGK_at_[hidden] (Ralf W. Grosse-Kunstleve)
>> 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 capricious
>> try to prepare the environment for all of them simultaneously.
>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.
Yes, and no. If the setup is in addition to the normal setup of the compiler
then it becomes an additional step the user has to do to use Boost. And we
certainly want to remove as many installation/setup barriers as we can. This
is the main reason we removed the need for environment vars, and why in V2
they will not exist at all.
The ideal is for the toolset to work with the default installation of a
compiler without user intervention.
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_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