Re: [jamboost] patch boost-base.jam project wide settings

From: Thomas Witt (witt_at_[hidden])
Date: 2002-02-26 12:40:17

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

On Tuesday 26 February 2002 18:22, Rene Rivera wrote:
> Would it then make more sense to reformulate the syntax so that it better
> fits the duality if the variant vs. requirement-set. What I'm thinking of
> is reformulating the syntax so that is looks more like variant.
> For example
> the following instead of Thomas' example:
>
> requirements TplBase
>
> <include>../myinclude
> <define>TEMPLATE
> ;
>
> requirements TplDerived : TplBase
>
> <include>../anotherinclude
> <define>DERIVED_TEMPLATE
> ;
>
> exe MyExe
>
> main.cpp
>
> <requirements>TplDerived
>
> debug
> ;
>

In the original proposal templates were handled similar to targets. They have 
a subproject-path. Do the proposed requirements work the same way i.e. does 
the following work:

file a.jam
- ---

project-root ;

requirements Req :
<define>REQROOT
;

file b.jam
- ---

subproject ping ;

requirements Req : ../Req
<define>REQPING
;

file c.jam
- ---

subproject pong ;

requirements Req : ../ping/Req
<define>REQPONG
;

I think using "global" names for req's is dangerous as name clashes are more 
likely with req's than with variants.

Thomas

> This way it would make adding the build settings extension easier. And
> makes the variant, requirements, and "settings"? all orthogonal.
>
>
> -- grafik - Don't Assume Anything
> -- rrivera_at_[hidden] - grafik_at_[hidden]
> -- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
>
>
> To unsubscribe from this group, send an email to:
> jamboost-unsubscribe_at_[hidden]
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
- -- 
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover
voice: [phone] - 4273, fax: [phone]
http://www.ive.uni-hannover.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8e8iF0ds/gS3XsBoRAm/+AJsEAx2rVI3Bg8yPsD/ReXoJNamGFgCaAv5B
Fue8cMcwrcjnSgTihHi6z/o=
=03Qg
-----END PGP SIGNATURE-----