Subject: Re: [Boost-build] bjam 4.0.. in C++
From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2010-05-24 09:43:33
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.
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" ?
-- ...ich hab' noch einen Koffer in Berlin...
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