From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: nativesdk and native recipe names
Date: Wed, 21 Dec 2011 11:55:05 +0000 [thread overview]
Message-ID: <1324468506.24417.278.camel@phil-desktop> (raw)
In-Reply-To: <1324465882.16323.13.camel@ted>
On Wed, 2011-12-21 at 11:11 +0000, Richard Purdie wrote:
> If we change nativesdk to become a prefix, the problem can share the
> same code as multilib and become much more widely usable rather than the
> current special cases. Its obviously a fairly major change in recipe
> naming though. Would changing this be acceptable?
I wonder whether we should just stop this business of bashing PN around
altogether and encode the native- or sdk-ness into PACKAGE_ARCH or some
such instead. (I guess this would need bitbake enhanced to be able to
build a parallel dependency tree for each architecture, and a way of
specifying the desired arch in DEPENDS, neither of which it can
presumably do at the moment.)
All these transforms on PN seem rather fragile and, although changing
the infix to be a prefix will help, it still doesn't completely
eliminate the chance of ambiguity.
p.
next prev parent reply other threads:[~2011-12-21 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:11 RFC: nativesdk and native recipe names Richard Purdie
2011-12-21 11:37 ` Otavio Salvador
2011-12-21 11:57 ` Anders Darander
2011-12-21 12:59 ` Richard Purdie
2011-12-21 11:55 ` Phil Blundell [this message]
2011-12-21 12:58 ` 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=1324468506.24417.278.camel@phil-desktop \
--to=philb@gnu.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