Re: [jamboost] Re: Conditional property validation

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2004-05-28 02:51:19

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi !
On Friday 28 May 2004 09:40, Vladimir Prus wrote:
> David Abrahams wrote:
> > > 1. Don't validate condition at all
> > > 2. Provide the means for user to say: 'msvc-7.1' is OK as the
> > > value. This, however, might be very tricky, since "msvc-7.1' is
> > > really a shortcut for
> >
> > 3. Automatically do "using msvc" the first time such a condition is
> > encountered. However, set things up so the toolset won't
> > complain about not finding the compiler.
>
> And how do we know
> 1. What toolset to load?
> 2. What version to configure?
>
> I'm thinking we better treat <toolset> in a special way and allow
> undeclared values of that feature.

I'm +1 for this, too. 
It is nearly impossible to support "standard" configurations for some 
20+ toolset with several subvariants.
For example.
I have 3 different gcc configurations already and have to disable some 
warning for gcc-3.4.0 (-Wno-deprecated) when evaluating this compiler.
My co-workers still use gcc-3.3.2 and do not even have 3.4.0 installed.
 
The same issue arises when testing other compilers ... (and commiting 
the Jamfiles, of course...)

Yours,

Jürgen

- -- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover  
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAtu93ljbJ/LLrxrYRAnzhAJ49558J8fLcfjXbi1LLQReDRdCT/gCgtYdI
mIazw866pOiFo+5sTS2220w=
=DNGy
-----END PGP SIGNATURE-----