Re: [Boost-build] building boost.python

Subject: Re: [Boost-build] building boost.python
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-05-08 14:01:50

AMDG

On 05/08/2015 11:45 AM, Stefan Seefeld wrote:
> 
> Is there a way for bjam (or boost.build) to detect the multiple
> initialization, and simply skip all but the first ?
> 

It's definitely possible to implement.

>>>
>>> As to the stand-alone build: should I just remove the boost-build.jam
>>> file entirely?
>> I think so.  If you're working inside
>> the boost tree, then you'll pick up
>> BOOST_ROOT/boost-build.jam.
> 
> Er, if I'm building stand-alone, I'm not inside the boost tree, and thus
> there is no boost-build.jam.
> 

Sorry, I didn't finish this statement.  If you're
building standalone, then you should be using
an installed Boost.Build which doesn't need
boost-build.jam.

>>> That yields the error "error: Unable to load Jamfile."
>>> (Do I really need both a Jamfile and a Jamroot ?)
>>>
>> No.  Is there any more to the error message?
> 
> The full error is:
> 
> /usr/share/boost-build/build/project.jam:262: in find-jamfile from
> module project
> error: Unable to load Jamfile.
> error: Could not find a Jamfile in directory '../../..'.

in python/example/Jamroot:
# Specify the path to the Boost project.  If you move this project,
# adjust this path to refer to the Boost root directory.
use-project boost
  : ../../.. ;

> <snip>
> 
> (The explicit '../../..' path above looks quite suspicious, as if
> boost.build made assumptions about the directory structure that aren't
> met in my stand-alone case.
> 

In Christ,
Steven Watanabe