Subject: Re: [Boost-build] third-party library dependencies
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-06-11 13:29:08
On 06/10/2018 07:29 PM, Stefan Seefeld via Boost-build wrote:
> On 06/10/18 20:41, Steven Watanabe via Boost-build wrote:
>> On 06/10/2018 06:38 PM, Stefan Seefeld via Boost-build wrote:
>>> With my faber frontend that's easy and natural, as modules are handled
>>> by Python, so all I need to do is set the PYTHONPATH variable. I would
>>> expect something equivalent with bjam, i.e. a simple search path where
>>> bjam will look for extension modules.
>> It's called BOOST_BUILD_PATH.
> OK, but what is the required "pre-build configuration step" you were
> mentioning in your last reply, then ?
You have to set BOOST_BUILD_PATH manually.
There's no way for a project to add itself
to BOOST_BUILD_PATH automatically, since
anything that the project does will happen
after user-config.jam is loaded.
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