From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-03-15 22:00:20
On 2002-03-15 at 09:47 PM, david.abrahams_at_[hidden] (David Abrahams) wrote:
>No, the bug is that somebody broke something!
>The original behavior of boost.build was to load any not-completely-read
>Jamfiles of dependencies with main target generation disabled so that it
>could collect the dependency info. That means that you can define lib
>dependencies after their dependents in the same jamfile -- it would
>re-include the jamfile to gather up the dependencies, then continue
>generating main targets.
Aha, didn't know that :-) I think the problem then is the guards against
multiple inclusion of Jamfiles is preventing that behaviour now. It still
includes dependendent Jamfiles, but it also prevents self inclusion. So if I
change those checks to allow self inclusion only it would bring back that
behaviour. Would that be the expected?
-- 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