From: Pedro Ferreira (pedro.ferreira_at_[hidden])
Date: 2005-03-04 10:05:16
On 4 Mar 2005, at 09:43, Vladimir Prus wrote:
> I've just got the minimal "make" example to work with bjam and the
> port. That is, running bjam invokes the Python port, which loads the
> and then build actions are run.
> Before committing this, there are a couple of questions to resolve.
> bjam loads Python modules it create an extension module "bjam". Any
> module can do
> import bjam
> bjam.call('some-bjam-rule', 'a', 'b')
> but "import bjam" means the module is only usable with bjam. Which
> gives two
> 1. I've added Jamfile loading to the ProjectRegistry code. Do you find
> desirable to split the logic into a separate module, so that
> project.py can
> be used without bjam? This should be easy -- just moving one class from
> project.py to another module, but maybe I worry too much?
If it isn't asking too much, I'd rather have it separate, please: I'd
really like to be able to create projects just using python.
> 2. Another issue is the BjamBuildSystem. Currently it generates the
> that is to be executed by bjam. I think now it's time to make it do
> calls to bjam. Is that OK with you? In my current version, calls to
> bjam are
> done via some kluge.
Sure. Just go ahead. I'm really looking forward to see it!
Lately I haven't had time to work consistently on the port but, slowly,
it's getting there: there already is minimal support for gcc and am
working on darwin right now.
I'll keep you all posted on this - more frequently than I have, or so I
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