Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-07-23 14:47:16

On Wednesday 23 July 2008 20:16:13 Juergen Hunold wrote:
> Hi !
> I've been experimenting with the PythonPort and got it working on Linux.
> Before I start hacking some more, I've just got a couple of question:
> 1) Which Unit Tests must I run in order to verify that I'm doing the right
> thing ? I've found test/ (the old bjam based testsuite, not working
> for me) and python/tests/unit_tests/ Both seem to require some
> magic to get them working. It would be nice if I could get some hints.

Right now, it's all manually tested.

> 2) Are there any design documents except
> ?

No, those are supposed to be the right one.

> 3) Shall I try to get everything working "as-is" ?

It's supposed that all existing code in Jamfiles work, with the exception of
the code that declares, or creates, classes, and maybe, calls to some util
functions that are gone.

> Rationale: I'm trying to build a rather large project in order to see if
> Python can speed up things a bit. The attached patch fixes my use-case
> |# rearrange default-features to shorten build paths
> |import feature ;
> |feature.set_default threading : multi ;
> to override the "single-threading" default of BoostBuild.
> What I'm seeing here is that
> a) BoostBuild currently uses "set-default" which is illegal in Python. Should
> I try to get some mapping logic implemented to improve compatibility ?

We just use _ in Python.

> b) Some design decision (see patch) are not clearly documented. I'm missing a
> clean rationale for most things except the implicit "do it like [b]jam way"

I'll be off for the night soon; I'll check your patch and reply tomorrow.

> I think I try and invest some time in porting testing.jam and then qt4.jam so
> I could get my programs to compile with Python on Linux.
> And last but not least: Should I try and get
> in sync with trunk/tools/build/v2 ? I think that the Boost.Build code there is
> rather old.

Are you sure? The current state is documented at

and most of the core modules are supposed to almost ported, and almost up-to-date.
Each file has a revision it was synced with, at the top, so it's easy to see if
jam conterpart was changed. Of course, moving those changes that were done is

- Volodya

> Yours,
> Jürgen

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at