Re: [PATCH, RFC] Link with $ORIGIN, mangle only when that's too hard, get it all

[Tom Rini <tom_rini@mentor.com>]

Tom Rini wrote:
> The following changes relocatable.bbclass to an always for native (and 
> disabled for cross) to an opt-in for hard to get right recipes.
> 
> With this, cross / native things like with $ORIGIN directly, for the 
> common case.  We do this as an in addition to so that programs that run 
> before install still work fine.  In addition doing this makes sure that 
> the initial RPATH will be long enough, even in the cross case, that we 
> can patch in a correct $ORIGIN[1].
> 
> Advantages? Less tasks, one less must have host utility (*cough*3rd 
> party yum repos*cough*).  Having an exists but not right second known 
> part of RPATH ensures cross recipes are now chrpath/patchelf patchable 
> and gets us one step closer to pstaging being relocatable (will have to 
> run some tests to look at the last corner cases).  Disadvantages? One 
> "ugly" escape sequence in bitbake.conf.

So for the moment, I need to retract this.  As soon as we hit a legacy 
do_stage, we go off and mangle everyone.  So more incentive to clear all 
of those out from -cross / -native :)  And as an aside, relocatable 
should use the relative function we have.  Will include that next time.

-- 
Tom Rini
Mentor Graphics Corporation