From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-04-05 05:46:53
> >From time to time we use to have some 'experimental' targets, which
> are not ready to be built on every machine in our development
> I'm using the explicit rule and marking these targets not to be
> built by default, with the intent to avoid disturbing the whole
> (default) build process.
> But when I'm building (sub)projects in my main project jamfile via
> the build-project rule, all targets, including explicit gets built.
> Is this an intentional behavior or a bug?
Looks like a bug. However, I cannot reproduce this on the attached example
using CVS version. Can you provide a small testcase that reproduces the
> I expected that build-project rule will behave the same way as
> invoking bjam with no target in the corresponding project's
> directory ...
Me too. In fact, they use exactly the same code path -- the generate method in
project-target class, so I have no idea why the problem you describe can
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2 --Boundary-00=_eymUCtAr9l3jumR Content-Type: application/x-zip; name="explicit.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="explicit.zip" [Attachment content not displayed.] --Boundary-00=_eymUCtAr9l3jumR--
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