Boost logo

Boost-Build :

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-08-28 11:01:01

Not that I have time to look into how to do this right now, but I
thought I'd bring it up for others to think about...

In testing I'm seeing some testers get this set of errors:

   warning: Python location is not configured
   warning: the Boost.Python library won't be built
   error: Unable to find file or target named
   error: '/boost/python//boost_python'
   error: referred from project at
   error: '../libs/parameter/test'

The reason for the error is obvious when looking at

   if [ python.configured ] {
     lib boost_python ...
   else {
     ECHO "warning: ...

Instead of not declaring the target it would be better to declare an
alternate target that will:

   * Fail unconditionally when it tries to build.
   * Gives some suitable message when it fails to build.
   * Has the effect of only adding a <dependency> to the dependents.

Perhaps something declared as:

   unavailable boost_python :
     "warning: Python location is not configured"
     "warning: the Boost.Python library won't be built"

This way dependent targets just fail to build instead of causing errors
that interrupt the overall build. Which in the testing case causes the
rather more appealing error boxes as opposed to no results.

-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. -
-- rrivera/ - grafik/
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

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