Re: [Boost-testing] Tried to build the target twice

Subject: Re: [Boost-testing] Tried to build the target twice
From: Dmitry Moskalchuk (dm_at_[hidden])
Date: 2016-07-17 17:19:54

On 17/07/16 01:44, Rene Rivera wrote:
> OK, I have a solution. It should now work that you can specify a
> target-os condition when configuring the python interpreter. The init
> for python.jam always had optional conditions for the interpreter, but
> unfortunately it was not usable for target-os because of the way it
> added the global toolset requirements. I've fixed that now. And I've
> also changed the Boost status/Jamfile to only use the host-os python
> interpreter accordingly. In your case all you need to do is add
> <target-os>??? when doing the "using python ..". That's assuming you
> build with "target-os=???". You might have to add a plain "using
> python ;" to configure the host-os python interpreter also, which is
> what the library check tests will use.

Thank you for help!

Yes, we're using "target-os=android" as b2 command line parameter.

However, something is still unclear. Just to confirm, do you mean adding
"<target-os>android" to "using python" directive in user-config.jam,
right? If yes, where exactly it should be added? Lets look on our "using
python" line:

using python : 3.5 : $PYDIR : $PYDIR/include/python :
$PYDIR/libs/armeabi-v7a ;

Could you please point me where to put "<target-os>android" exactly? I'm
asking this just because it's still unclear for me even after looking on
your commit
(https://github.com/boostorg/build/commit/78ffbe094400d277627b2c19ceb182d637b8baca),
and I know how sensitive bjam to syntax of Jamfiles (even spaces are
important!), so I can easily break everything, and edit-build-run loop
is too long to just try and see.

-- 
Dmitry Moskalchuk