Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Heads up: xxx-nativesdk -> nativesdk-xxx change
Date: Sat, 25 Aug 2012 17:46:53 +0100	[thread overview]
Message-ID: <1345913213.14369.131.camel@ted> (raw)

As was previous discussed on the list a while ago, we have a problem
with nativesdk where the code is getting complex and convoluted as its
simply not possible to automatically "extend" using a suffix.

Extension using a prefix works comparatively well be comparison as shown
by the multilib code. Its for this reason I'd like to switch the
meta-toolchain nativesdk recipes to become a prefix rather than a
suffix.

I'm going to propose some patches soon that do this. The patches are
fairly nasty to write and maintain so will need to merge fairly quickly.

If anyone does have a strong objection to this change, now is the time
to raise it. I'd prefer not to have to do this but having considered all
the options, its the best thing to do for the future and will result in
cleaner metadata (look at PKGSUFFIX in eglibc for an example of how
messy this gets).

Note that -native are unchanged and there is no problem or planned
change which them, this just affects nativesdk.

An example WIP patch is:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t1&id=2aa1acf11dd26bc194668be81544d08ab5e9bb24

Cheers,

Richard




             reply	other threads:[~2012-08-25 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25 16:46 Richard Purdie [this message]
2012-08-25 20:25 ` Heads up: xxx-nativesdk -> nativesdk-xxx change Khem Raj
2012-08-25 20:59   ` Chris Larson
2012-08-25 21:00   ` Richard Purdie
2012-08-25 21:14     ` Khem Raj
2012-08-26  8:34       ` Richard Purdie

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=1345913213.14369.131.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox