|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-17 09:28:31
Rene Rivera wrote:
> >> Just last night I checked in the integration of the load behaviour :-)
> >
> >Fabulous! What should I look at?
>
> Most of the changes are in project.jam, and project-root.jam (added). I
> also added a print.jam, which has the print rules that where in doc.jam.
> This is to do what Valadimir did with the dump rule but for in a more
> modular way
Rene, I generally like your changes. Thanks!
I have two problems and one feature request
1. There is project.module-name rule which you don't use anymore. That rule
is
needed to make project.lookup work. Would be reasonable to
just change that rule to return whatever you like and use it when
you need to make module name for Jamfile module.
2. find-jamfile rule contains:
if ! [ os.path.is_rooted $(jamfile) ]
{
local root-path = [ os.path.parent [ os.path.make
[modules.binding [ CALLER_MODULE ] ] ] ] ;
normalized =
[ os.path.native [ os.path.root_relative_path $(jamfile)
$(root-path) ] ] ;
}
I'm afraid that this is not going to work. Caller module will most likely be
'project',
and path of that module is not what you want. Also, why should be root jamfile
paths? I thought that referring to jamfile modules using they locations
relatively to jam invocation dir is something that we'd like to have.
3. (feature). I think it would be great if 'site.jam' and 'user.jam' were
loaded prior
to loading Jamfile. I guess we'd need that feature in the very near future.
And also, since now Jamfiles are loaded using project.load, I've changed
test.jam to include all the necessary bootstrapping.
- 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