Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: "openembedded-core@lists.openembedded.org oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Architectures with underscores in their names, how to handle that?
Date: Thu, 10 Oct 2013 07:56:01 +0100	[thread overview]
Message-ID: <1381388161.29912.67.camel@ted> (raw)
In-Reply-To: <D14FF4AA-C9DA-40C4-B706-3953E31F1A35@dominion.thruhere.net>

On Thu, 2013-10-10 at 08:27 +0200, Koen Kooi wrote:
> Hi,
> 
> I'm working on adding support for big-endian armv8 and the toolchain
> people decided that it should be named 'aarch64_eb'. That currently
> works in OE because there isn't a 'eb' override yet, but there might
> be one in the future.
> 
> So my question is, how can I safely handle a name like this?

I suspect we'll just have to be careful never to add an "eb" override,
in much the same way as a 64 override would also cause problems for
x86_64. There is code in place to change the _ to - for package feed
use.

Longer term I'd like to see us find a better character for overrides
than the current use of "_" but that would be a fair bit of work to
achieve. I'd like to think that would performance as well as readablity
of .bb files but I've yet to prove it.

Cheers,

Richard



      parent reply	other threads:[~2013-10-10  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  6:27 Architectures with underscores in their names, how to handle that? Koen Kooi
2013-10-10  6:30 ` Khem Raj
2013-10-10  8:34   ` Fathi Boudra
2013-10-10  6:56 ` 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=1381388161.29912.67.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.net \
    --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