Making BBv2 transition easier... Was: [jamboost] Re: Python + bjam: some questions

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-03-05 12:13:21

David Abrahams wrote:

> This is all great, and I hate to be a spoilsport, but we really need
> to retire BBv1 and replace it with BBv2 before having any more fun
> with Python. I can't overemphasize how important this is!

Speaking of that.. I'm going to bring back the subject about file names.

I'm not particularly fond of Jamfile/Jamrules(.v2), etc. And it would be 
nice if we could start "officially" moving Jamfiles to BBv2 to help the 
transition.

So here's what I'm thinking:

1. Use "build.jam" as the project files, instead of Jamfile(.v2). The 
name is short, direct to the point, and relates closely to Boost.Build.

2. Change the Jam load behavior so that if Jam is run as "b2jam" it 
invokes BBv2, instead of "--v2".

Was there a resolution re: the "project-root.jam" file?

I know it's more changes but we really need to start moving the Boost 
build files towards BBv2.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq