Subject: [Boost-build] Debugging how bjam determines build properties
From: Anthony Foglia (AFoglia_at_[hidden])
Date: 2010-05-12 19:32:42
Is there some reasonable way to debug how bjam determines the build
properties of the request. I've been discovering some real screwy
oddities with the build bjam makes, and the debug information from
--debug-building is just way too much information for a human to parse.
My current problem is that the target has some dependencies which have a
common library dependency, which is defined with the requirement
<link>static, the usage-requirement <link>static, and included in the
libraries which use it with a /<link>static, yet still bjam wants to use
a .so version.
(An earlier problem was that bjam was compiling sourced in
multi-threaded that I explicity removed from the sources in such case,
but only under certain conditions.)
There has to be a better way than trying to parse 2000 lines of output.
Does someone have some sort of script perhaps to parse the output of
--debug-building? Or are there other command line options?
-- Anthony Foglia Princeton Consultants (609) 987-8787 x233
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