Re: [Boost-build] bjam 4.0.. in C++

Subject: Re: [Boost-build] bjam 4.0.. in C++
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2010-05-24 10:31:26

On 5/24/2010 8:43 AM, Stefan Seefeld wrote:
> On 05/23/2010 06:29 PM, Rene Rivera wrote:
>>
>> How about this approach..
>>
>> 1. Start of with a Spirit parser as the quick way to get going.
>> 2. Work out the API and accompanying testing.
>> 3. Create another C++ non-Spirit parser when the core is working.
>> 4. Create some other non-C++ front-end.
>> 5. Abandon, or keep as an example, the Spirit front-end.
>
> You are suggesting to use a spirit-based parser as a frontend prototype
> to help figure out API-level requirements on the "core" library. That
> sounds like a good idea.
>
>>
>> The assumption would be that the core would avoid depending on Boost.
>> There's one lib I will want to depend on but it's my Predef lib which
>> is not part of Boost yet anyway :-) But there may be other libs I end
>> up creating along the way. So I guess we can think of this as the
>> library structured version of bjam.
>
> Echoing what has already been said by others: Being very portable and
> having few external dependencies is important for a build tool, if it
> wants to be widely popular. It might be good to integrate any
> dependencies right into the code (repository), to make this easier.

That was always the plan.

> By the way: it sounds as if this will be an entirely new tool, so why
> not reflect that fact in a new name, instead of "bjam N+1" ?

I've been trying to think of a name for some time now.. Nothing 
brilliant has come up. The one suggestion I had when Volodya asked 
names, was to just call the binary "build" (or build.exe). As that name 
seems to not be taken :-) And it would be counter to "make" ;-) But 
that's just the executable name, and doesn't really have much to do with 
the project name. And perhaps it's the best name for the EXE since it's 
real use is with Boost Build v2 and full integration is next on the todo 
list. But having a sub-project name for the tool project would be nice.

Hence, naming suggestions are very much welcome!

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail