From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-09 03:55:05
in the past, I used to ask users for output of "bjam -d+10" to know what parts
to optimise. That was helpful and I've made a number of optimisations, but
still it's not very effective.
To be able to try different approaches quickly, I need to have testcases I can
play with locally, without waiting for fresh profiles from users. It's best
to test on Boost.Build setup used on real projects.
However, you probably don't want to send me your entire project, so I wrote a
small script to extract Boost.Build setup. The idea is that:
1. You make a copy of your real project.
2. You run the script in the copy. All non Boost.Build files are truncated to
zero size. This way, Boost.Build won't complain about missing sources, but
the content is removed.
3. You pack the resulting directory and send it to me.
The python script is attached. It's pretty simple, and even has unit tests for
I'd appreciate as many testcases as possible. I don't plan to add them to CVS
or make them public (unless you explicitly indicate making them public is
OK). Only I will see them.
In addition to testcase, I'd need to see your user-config.jam and
site-config.jam (in case you have some definitions there which are required
for the project to build).
I'd also appreciate information about time "bjam -n" takes on your project and
hardware details (CPU, memory size, disk speed).
Thanks in advance. I hope that with testcases Boost.Build will soon get faster
on *your* project.
--Boundary-00=_pLBuBYKxkX4HsS0 Content-Type: application/x-python;
[Attachment content not displayed.] --Boundary-00=_pLBuBYKxkX4HsS0--
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