From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2006-08-14 02:30:48
Alex Besogonov wrote:
>>> # Add 'tools' directory to module search path.
>>> local x = [ modules.peek : BOOST_BUILD_PATH ] ;
>>> modules.poke : BOOST_BUILD_PATH : $(TOP)/build/tools $(x) ;
>>> We need something better and more user-friendly.
>> I'm not sure I understand what you want. Where is the above
>> "build/tools" located? How does it relate to the external library
> I have a project which uses some project-specific jamscripts (test
> harness) in $(PROJECT_TOP)/build/tools directory, but BBv2 has no
> means to specify additional search directories for jamfiles. The best
> solution I've found is direct modification of BOOST_BUILD_PATH.
> If we are going to add a separate project which will likely be located
> outside of the Boost source tree on users' machines then we need means
> to modify search paths without such hacks.
FWIW, I've been doing the exactly same thing myself. It works fine, but is
admittedly a bit awkward to use. How about adding something like
'add-search-path' to modules.jam?
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