|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-08-06 02:16:06
Rene Rivera wrote:
> [2002-07-08] Vladimir Prus wrote:
> >Second, this issue involves some changes to project root handling.
> >
> >1. Maybe, we should move all project-root related data into separate
>
> object,
>
> >so that proejct root module namespace be clean as well.
>
> Done, finally ;-)
Thank you!
> >2. We'd need to make the "use-project" rule available in project root
> >namespace. (I'll document that rule in the user docs soon. You can refer
> > to the thread starting with
> >http://groups.yahoo.com/group/jamboost/message/1320 meanwhile)
>
> Done. Although I don't know how well of a test I put in is. I just put a
> use-project in the project-root.jam of project-test3/lib3.
I've added an additional test -- that the declared project id can be used to
refer to targets. Test passes.
> >3. We'd need to import non-local rules from project root module into
>
> jamfile
>
> >modules.
>
> Do you want me to bounce you the sourceforge task and you work on that one?
> Or do you want me to work on it?
I like the second variant better ;-) I'm going to change feature attributes a
little soon, per documentation in boost_build_v2.html.
> Either way one issue is... When should the
> rules be imported? The three choices I see are: 1) in new/project-root.jam
> before the project gets loaded; 2) in new/project.jam before loading the
> project, but after creating the project module; or 3) after the project is
> loaded.
>
> #3 Looks obviously like the wrong choice. As that would remove the benefit
> of the user declaring the rules :-)
>
> Choosing between #1 and #2 is only a choice of where we think the code
> should be, as it seems to be both project-root and project code.
I favour #2, although don't know why.
- Volodya
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