Re: [Boost-build] Native-built tools in a cross-compile environment

Subject: Re: [Boost-build] Native-built tools in a cross-compile environment
From: Nogradi, Chris (Chris.Nogradi_at_[hidden])
Date: 2012-10-23 15:52:49

On Tuesday, October 23, 2012 2:37 PM, Steven Watanabe wrote:

> The problem is in Boost.Build's handling of static libraries (In some
> cases, static libraries can be propagated upwards too far):

> I've made a reduced test case for this that works with any toolset.
> I'm not exactly sure how to go about fixing it yet, though.

I suppose my suggestion referenced below was not reasonable?  Or maybe it is a different issue though it sounds similar?

> On 01/12/11 01:24, Nogradi, Chris wrote:

> > What I ended up doing is to modify targets.jam line 1421 like so:
> >
> >          # TODO - Actually there are more possible candidates like for instance
> >          # when listing static library X as a source for another static library.
> >          # Then static library X will be added as a<source>  property to the
> >          # second library's usage requirements but those requirements should last
> >          # only up to the first executable or shared library that actually links
> >          # to it.
> >          local raw = [ $(subvariant).sources-usage-requirements ] ;
> >          raw = [ $(raw).raw ] ;
> >          raw = [ property.change $(raw) :<pch-header>  ] ;
> >          raw = [ property.change $(raw) :<pch-file>  ] ;
> >
> >            # remove libraries from shared link targets
> >              if <link>shared in [ $(rproperties).raw ]
> >          {
> >              raw = [ property.change $(raw) : <library> ] ;
> >          }
> >          return [ $(result).add [ property-set.create $(raw) ] ] ;

Thread references:

http://thread.gmane.org/gmane.comp.lib.boost.build/24424/focus=25122
http://article.gmane.org/gmane.comp.lib.boost.build/25122/match=nogradi

Thanks,

Chris

________________________________

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.

Thank you for your cooperation.