From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-01 05:43:00
> Let us take Boost itself as an example.
> In my project-a I state
> use-project /boost : path-to-boost ;
> The current Boost Jamfile.v2 contains several build-project rules which
> bjam happily follows and add _their_ usage-requirements, too.
> (for concrete output see setup/procjec-b/actions.txt)
> Unfortunately, this results in _all_ Jamfiles of project-a being
> examined because they are _all_ referenced for the apps in project-a.
> And this is _slow_. _Very_ slow.
> Not in the test-case because it simply has no "real" input and not
> enough libs. But for my project it really hurts.
> There are two possible solutions:
> a) don't follow build-project when "use"ing a Jamfile.
> b) make V2 faster. _Much_ faster
Probably, there's another solution. Boost (and your project-a), should havea
target defined in top-level Jamfile:
alias includes ;
Of course, I'd like V2 to be lighting fast so this is never needed ;-)
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