From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] meta-toolchain: make SDK relocatable by using $SDK_PATH var in env setup script
Date: Mon, 08 Feb 2010 23:31:53 +0000 [thread overview]
Message-ID: <1265671913.26725.374.camel@rex> (raw)
In-Reply-To: <20100204190730.GB5641@denix.org>
On Thu, 2010-02-04 at 14:07 -0500, Denys Dmytriyenko wrote:
> On Thu, Feb 04, 2010 at 01:42:50PM -0500, Chris Conroy wrote:
> > 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.
>
> All I was trying to say is that, while it's a valid question, it is out of
> scope of this patch. I don't want to mix 2 things in one patch (if we decide
> to remove one of SDKPATH/SDK_PATH). And it would still be good to hear RP's
> rationale.
As best I remember, historically, there was SDK_PREFIX. When we created
the SDK_ variables, this conflicted with things like TARGET_PREFIX,
HOST_PREFIX and BUILD_PREFIX so it had to be renamed. OE went with
SDK_PATH, Poky went with SDKPATH. When I merged a load of toolchain
stuff between the two, I think I realised halfway through a merge there
was a problem and inserted that variable to make sure everything worked.
I'm sure I intended to clean it up at some point but never got around to
it.
In summary, one needs to go.
I have a preference for not having an underscore in the name as SDKPATH
does something different to the other SDK_*, TARGET_*, HOST_* and
BUILD_* variables and does not have a counterpart.
Cheers,
Richard
prev parent reply other threads:[~2010-02-08 23:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 1:43 [RFC][PATCH] meta-toolchain: make SDK relocatable by using $SDK_PATH var in env setup script Denys Dmytriyenko
2010-02-04 16:57 ` Chris Conroy
2010-02-04 17:22 ` Denys Dmytriyenko
2010-02-04 17:57 ` Tom Rini
2010-02-06 13:04 ` Phil Blundell
2010-02-08 19:00 ` Tom Rini
2010-02-09 20:08 ` Khem Raj
2010-02-09 21:36 ` Tom Rini
2010-02-10 15:50 ` Richard Purdie
2010-02-10 18:45 ` Tom Rini
2010-02-10 18:54 ` Phil Blundell
2010-02-04 18:42 ` Chris Conroy
2010-02-04 19:07 ` Denys Dmytriyenko
2010-02-08 23:31 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1265671913.26725.374.camel@rex \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.