Boost logo

Boost-Build :

From: Bojan Resnik (resnikb_at_[hidden])
Date: 2006-09-07 05:49:15

> It would be nice to have an explicitly stated policy for dealing with
> defaults. This is needed for both the users and the developers. For
> users to know what you get by default, for the developers to guide the
> implementation.

  As I see it, there are two sets of default options: compiler's and
boost build's. These two are not related, meaning that an option may
be the default in boost build, regardless of its status in the
compiler. The only time an option can be omitted on the command line
is if it is default in both the compiler and boost build, which would
require that boost build is aware of the compiler's defaults . Again,
as the compiler defaults may change from version to version, there
must be additional code in boost build to define the defaults for each
of the supported versions. IMHO, this would only unneccessarily
clutter the code, while not adding any value.

  Regardless of whether the compiler's and boost build's defaults are
the same, the user must be aware of them and explicitly specify
additional options if the defaults are not suitable.

Bojan Resnik

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at