Subject: [Boost-build] Library dependency include order
From: Norbert Wenzel (norbert.wenzel.lists_at_[hidden])
Date: 2015-08-03 05:21:41
I've recently written already to the Boost.Dev ML but it seems the
problem is more related to Boost.Build in general than to a specific
The problem is that, depending on the order I include my subprojects,
the build either fails or succeeds. I've set up a little testproject
to illustrate this (and my poor Boost.Build skills).
As you can see in the Jamfile the 'test' and the 'fail' project only
differ in the include order of the 'testlib'. This setup builds fine
when using Boost 1.57 but fails with 1.58, since Boost.Log switched to
Boost.Config between that releases.
To me it seems that the settings determined by Boost.Config are not
My question is now, if this is a problem in Boost.Build,
Boost.Log/Boost.Config or in my test project. Is it advisable to include
Boost.Config (or maybe all Boost libs) before any other libraries, that
might again include some Boost libs?
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