From: David Abrahams (dave_at_[hidden])
Date: 2004-06-11 13:54:20
Vladimir Prus <ghost_at_[hidden]> writes:
> I've tried to document the way toolsets are initialized, and figured out
> there's some inconsistency from platform to platform.
> 1. Some toolsets allow the specify the name of compiler (including path, if
> needed), e.g:
> using gcc : 3.3 /usr/bin/g++-3.3 ;
> Some other require to pass "installation root", e.g.
> using msvc : : P:\.....\vc98 ;
That's just the equivalent of path for that compiler. I see that
toolset as needing resources (including the compiler executable) in
multiple subdirectories of that installation directory.
> 2. For all compilers but gcc, the path is specified as a separate parameter,
> but gcc specifies it in the same parameter as version, i.e. it uses
> using gcc : 3.3 g++-3.3 ;
> as opposed to
> using gcc : 3.3 : g++-3.3 ;
> I believe this inconsistency is bad, and propose that:
> 1. Gcc is changed to match other compilers.
> 2. All toolset accept name of the compiler, and not some installation root.
> This would make it simple to explain how toolset is to be initialized.
How will the directory for a nonstandard installation be specified, then?
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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