Re: [RFC][PATCH] meta-toolchain: make SDK relocatable by using $SDK_PATH var in env setup script

[Chris Conroy <Chris.Conroy@hillcrestlabs.com>]

On Thu, 2010-02-04 at 12:22 -0500, Denys Dmytriyenko wrote:
> First of all, they are the same. Check conf/bitbake.conf:
> 
> SDKPATH = "${SDK_PATH}"
> 
> Second, ask RP why he introduced SDKPATH, when we had SDK_PATH for years (my 
> guess - that's what is used in Poky, so makes porting changes easier):
Fair enough, but saying 'ask RP' doesn't justify away the fact that
having these two variables is confusing. If they really are the same,
then one should be removed. If one shouldn't be removed, then there is
some difference that should probably be documented. It's just a matter
of consistency/readability.

> 7c2bd627 (Richard Purdie  2009-11-12 11:51:18 +0000 342) SDKPATH = "${SDK_PATH}"
> 
> > renamed since having them both will be a source of confusion.
> > 
> > It should probably be ${SDK_PATH} instead of $SDK_PATH in your changes.
> 
> You missed the whole point of the patch. It really should be $SDK_PATH
My bad there. I got hung up on the SDK_PATH/SDKPATH thing.

> 
> > Does this really make the SDK relocatable? I thought there were still
> > major issues with relocating GCC.
> 
> GCC built from OE may still have relocation problems - haven't checked lately.
> But it doesn't mean that's the only use case scenario... There is also 
> external toolchain option, as well as building SDK without the toolchain.
> Both of those cases were tested with the above change for several months now.
>