From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-03-04 04:43:39
I've just got the minimal "make" example to work with bjam and the Python
port. That is, running bjam invokes the Python port, which loads the Jamroot,
and then build actions are run.
Before committing this, there are a couple of questions to resolve. Before
bjam loads Python modules it create an extension module "bjam". Any python
module can do
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 it
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?
2. Another issue is the BjamBuildSystem. Currently it generates the string
that is to be executed by bjam. I think now it's time to make it do real
calls to bjam. Is that OK with you? In my current version, calls to bjam are
done via some kluge.
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