Re: [jamboost] Re: Refactoring progress report

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-05-13 01:34:49

[2003-05-13] Vladimir Prus wrote:

>Ali Azarbayejani wrote:
>
>> My point was you can't have
>> simple projects with just the Jamfile. Compare to "make"...all the
>> simple things for simple projects that you can do with "make"
>> shouldn't be hard or more complicated to do in Jam/BBv2. One of these
>> simple things is creating a single build description file to build a
>> simple program.
>
>Ok, I understand what you're after.
>
>> > > At the logical BOOST_ROOT/project-root.jam.
>> >
>> > Yes, that's precisely what we're saying. Ali's usage model is not one
>> > which needs or wants subprojects most of the time, and the arrangement
>> > where each project can stand on its own is a very important model.
>>
>> Yes. Most software modules of mine stand on their own or can be part
>> of a bigger tree (or many different trees). So each module must be a
>> project in its own right and by the current implementation requires
>> not only a Jamfile but also its own project-root.jam. This is
>> annoying.
>
>Got this too. Thanks for making this clear.
[snip]
>I buy this argument. Not partial about new name of project-root.jam, but 
>Jamfile is nice, so probably Jamroot is ok.

Yes, thanks for making it clear now :-)

I've been thinking about this for a while and here's what seems most
reasonable to me.

1. Yes, the project-root.jam name seems unintuitive now. I'm the one who
suggested it initially and in my projects it makes sense because I name my
"Jamfile"s "project.jam". In keeping with the new naming I would suggest we
instead use the Jamroot idea from Ali. Specifically that we look for
"[Jj]amroot" or "[Jj]amroot.jam". And correspondingly with jamfiles we have
a JAMROOT global to set the match pattern.

2. That we modify the load sequence to allow not having a Jamroot file...

a. We do the regular search for the Jamroot file, if found great.
b. If not found we create a "fake" project-root where the Jamfile is
located, that is the current dir. Along with this we might want to issue a
warning indicating the lack of a formal Jamroot file.

This only requires some minor changes to the project-root class to
support a no-load creation/initialization. I'm sure there qould be changes
elsewhere, like in project.jam, but not sure what those are.

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq