Eggleton [paul.eggle...@linux.intel.com]
> *Sent: *Monday, June 24, 2013 08:31 AM Pacific Standard Time
> *To: *Hatle, Mark
> *Cc: *openembedded-core@lists.openembedded.org
> *Subject: *Re: [OE-core] [PATCH] buildtools-tarball: Change the way the
> SDK is sanitized
>
> On Mon
]
Sent: Monday, June 24, 2013 08:31 AM Pacific Standard Time
To: Hatle, Mark
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] buildtools-tarball: Change the way the SDK is
sanitized
On Monday 24 June 2013 09:47:15 Mark Hatle wrote:
> + script=${1:-${SDK_OUTPUT}/
On Monday 24 June 2013 16:31:13 Paul Eggleton wrote:
> On Monday 24 June 2013 09:47:15 Mark Hatle wrote:
> > + script=${1:-${SDK_OUTPUT}/${SDKPATH}/environment-setup-${SDK_SYS}}
>
> I could be wrong but I think this may be a bashism...
Actually, I spoke too soon, it isn't. Ignore me...
Cheers,
On Monday 24 June 2013 09:47:15 Mark Hatle wrote:
> + script=${1:-${SDK_OUTPUT}/${SDKPATH}/environment-setup-${SDK_SYS}}
I could be wrong but I think this may be a bashism...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
O
The previous method of shrinking down the scale of the environment-setup
file would not work properly when the target is configured with multilibs.
In addition, the configured machine name and similar settings could leak
into the SDK naming. This was resolved by clearing the SDK generated
files a
