Boost logo

Boost-Build :

From: jwulp_at_[hidden]
Date: 2006-11-24 06:15:27


Hello Everyone,

I am currently involved in doing maintenance on the MCRL2 toolset. This is a set
of tools build on top of a variety of libraries such as ATerm, SVC, libXML,
wxWidgets, and a couple more. The fundament consists largely of the ATerm
library; so almost all tools use it therefore there is a strict dependency. The
toolset cannot be build without the ATerm library. No problems so far.

The problems start when there is a hierarchy of libraries and somewhere
below in the hierarchy a library is not available. Using the build feature the
lower level library has <build>no in its requirements (and usage requiements).
The build feature is nicely propagated upward following the reverse dependencies;
but it has no effect. Tools as well as libraries are still being build with a
directory element build-no in the target names.

Is there a reason why the <build>no does not have an effect when it is added via
usage requirements? Is there another way to achieve the desired effect?

Thanks an advance for any help.

Best regards,

Jeroen


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