Re: [Boost-build] Built tools and cross compiling

Subject: Re: [Boost-build] Built tools and cross compiling
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-12-21 17:23:26

AMDG

On 12/20/2015 12:26 AM, Tom wrote:
> 
> In the broader case, I want the requirements
> specified explicitly on a target in the Jamfile to be used and not
> those given on the command line.  This may not be a reasonable
> expectation for Boost.Build.
> 

  That's how Boost.Build is supposed to work.
If it doesn't it's either a bug or because
you didn't specify what you were trying to
specify.

>>   Would it be sufficient for your use case simply to
>> reset the toolset and all related features to their
>> default values for built_tool, completely ignoring
>> both the command line and the explicitly specified
>> cross-compiler?  I know this isn't perfect, but it's
>> easy to implement, and if it's good enough, it's probably
>> not worth the difficulty of somehow propagating the
>> command line toolset through.  (The default means
>> that you'll use the first toolset defined in any
>> config file).
> 
> This is probably good enough for this use case.

  Okay.  To do this you'll need to write
a custom target.  You can use the definition
of alias in build/alias.jam as a base.
Basically, you need to override either
generate or generate-dependencies and
delete the relevant properties from the
property-set before forwarding to the base
class implementation.  The implementation
will then automatically fill in the
defaults again.

>
> <snip>
> 
>> <snip>Is this with
>> fa54f3c?
> 
> I can't find fa54f3c.  Is that a commit in boostorg/build?
> 

It's in your example repository.

In Christ,
Steven Watanabe