[OE-core] Generating a movable SDK

[Richard Purdie]

On Wed, 2012-07-04 at 08:43 +0200, Tasslehoff Kjappfot wrote:
> On 06/20/2012 08:03 AM, Tasslehoff Kjappfot wrote:
> > On 06/19/2012 10:33 PM, Khem Raj wrote:
> >>
> >>
> >> On Tuesday, June 19, 2012, Steve English <steve.english at navetas.com
> >> <mailto:steve.english at navetas.com>> wrote:
> >>  > Hi,
> >>  > I've generated a cross compiling ARM SDK
> >> (angstrom-eglibc-x86_64-armv7a-v2012.05-toolchain.tar.bz2) that works
> >> great if installed in /usr/local/oecore-x86_64. I would like to move
> >> these binaries and run them from under my home directory (on this and
> >> other host machines).
> >>  >
> >>  > I can tweak the PATH and use --sysroot where appropriate, but the ELF
> >> binaries themselves specify a loader of
> >> /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/ld-linux-x86-64.so.2
> >>
> >> in their .interp header. Is it possible to generate an SDK that uses the
> >> standard host loader, or at least uses a relative path for the built
> >> loader?
> >>
> >>
> >> Sdk is not install time relocatable yet there is a feature enhancement
> >> request in yo to bugzilla for the same
> >>
> > That request is mine, I think. I have gotten around this by making
> > /usr/local/oecore-i686 a symlink to where I want to keep the toolchain
> > (in a vcs). Works like a charm.
> >
> > - Tasslehoff
> 
> But now I wish the sdk was relocatable again.
> 
> As I said we have the sdk in our vcs, and a symlink in /usr/local to 
> make the toolchain binaries happy. We have a build server that does 
> continous builds, and she has multiple trees checked out, so the 
> symlink-approach is not ideal.
> 
> Any clever workaround for this (or even better, a fix to make the sdk 
> relocatable)?

There is work underway to make it relocatable as part of the 1.3
release:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2383

Cheers,

Richard