From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-03-31 11:52:29
On 2002-03-31 at 08:46 AM, david.abrahams_at_[hidden] (David Abrahams) wrote:
>----- Original Message -----
>From: "Rene Rivera" <grafik666_at_[hidden]>
>> On 2002-03-30 at 09:21 PM, david.abrahams_at_[hidden] (David Abrahams)
>> >Question: what is a "module-tag" supposed to be?
>> It's the tag to use to identify the module as being loaded or not.
>> "load-tag" is better? Any suggestions welcome :-)
>Why can't it always be derived from the module-name? Every module must
>have a unique identifier anyway. I'm sure you have a reason, but please
>spell it out...
To be specific, I need to call load to load the Jamfiles, but they need to be
in the module of the project-root...
modules.load <project-root-module> : <Jamfile> : <some-jamfile-dir> :
So it will include the Jamfile inside the <project-root-module> but use the
<some-jamfile-dir>/<Jamfile> to decide wether it's been loaded already or not.
Maybe a name closer to C++ might help, how about "module-key"?
>> Question, is there a way to get the argument template of a rule? ...So
>> print it as part of a rule's doc.
>HDDRULE, HDRSCAN, baby. I'm telling you, doing doc dumps as build
>actions has lots of advantages. You could even extract doc from comment
>blocks, so there's no issue with interpretation of $() or space/newline
>(though I guess strings work pretty well in Jam).
:-) ... but you can't handle --help* with HD* ;-\
-- 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