Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] RFC Distro config changes
Date: Wed, 11 May 2011 11:54:24 +0100	[thread overview]
Message-ID: <1305111264.30391.338.camel@rex> (raw)
In-Reply-To: <D098457C-E05A-40F8-A61C-36604A51A2E1@dominion.thruhere.net>

On Wed, 2011-05-11 at 12:13 +0200, Koen Kooi wrote:
> Op 11 mei 2011, om 11:45 heeft Richard Purdie het volgende geschreven:
> > For the uclibc bits, I'm proposing
> > to add:
> > 
> > +DEPLOY_DIR_append = "-uclibc"
> > +STAGING_DIR_TARGET_append = "-uclibc"
> > +STAGING_DIR_HOST_append = "-uclibc"
> > +SSTATE_MANIFESTS_append = "-uclibc"
> > 
> > to tclibc-uclibc.inc.
> 
> Can we use _append_libc-uclibc = "uclibc" or even plain ${TCLIBC} in a
> generic include file? That would be a lot more readable and fix glibc
> vs eglibc.

Changing uclibc around is ok as its not something that has worked well
in with OE-Core for a while. What I'm trying to avoid is having to bump
all the versions of the sstate files, the sysroot layout and associated
version numbers which is what would have to happen if we change the
eglibc layout :(.

Obviously, if angstrom switches layout its pain for you though so I
suspect someone loses with this either way :/.

> > For the SDK/TOOLCHAIN bits, I need to have a close look at the SDK and
> > figure out what the implications are there as I want to ensure that they
> > can all be parallel installed as well as being in separate tarballs but
> > its something we need to look at.
> 
> I needed 'armv5te' and 'armv7a' in the tarball name, so that's how
> this is derived. It matched the OE names, but Khem found some bugs and
> changed it a little.

Makes sense and I see the need, I just want to ensure the tarballs we
have can be parallel installed.

Cheers,

Richard




  reply	other threads:[~2011-05-11 10:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 14:00 [PATCH 0/6] RFC Distro config changes Richard Purdie
2011-05-10 14:00 ` [PATCH 2/6] bitbake.conf: Include the new default-providers.inc and default-versions.inc files Richard Purdie
2011-05-10 14:20   ` Koen Kooi
2011-05-11  9:09     ` Richard Purdie
2011-05-11 10:08       ` Koen Kooi
2011-05-11 11:24         ` Richard Purdie
2011-05-11 11:43           ` Koen Kooi
2011-05-11 13:34             ` Richard Purdie
2011-05-10 14:00 ` [PATCH 1/6] Drop poky-floating-revisions.inc, poky-bleeding.conf and poky-lsb.conf Richard Purdie
2011-05-10 14:00 ` [PATCH 6/6] preferred-xorg-versions.inc: Drop this, it makes no sense given we only have one version of these recipes Richard Purdie
2011-05-10 14:00 ` [PATCH 5/6] conf/distro/include/default-distrovars.inc: Create set of default 'distro' variable values Richard Purdie
2011-05-10 14:26   ` Frans Meulenbroeks
2011-05-10 19:26     ` Richard Purdie
2011-05-11 11:51       ` Frans Meulenbroeks
2011-05-15 20:48   ` Khem Raj
2011-05-19 22:51     ` Richard Purdie
2011-05-10 14:00 ` [PATCH 4/6] machine/qemu: Add qemu-config as an essential machine speicfic dependency and drop specific distro config Richard Purdie
2011-05-10 14:00 ` [PATCH 3/6] distro: Add defaultsetup.conf, a set of default configuration providing sane overrridable default for commonly used options Richard Purdie
2011-05-10 14:31   ` Koen Kooi
2011-05-11  9:37     ` Richard Purdie
2011-05-15 22:28       ` Khem Raj
2011-05-10 14:05 ` [PATCH 0/6] RFC Distro config changes Frans Meulenbroeks
2011-05-10 14:08   ` Richard Purdie
     [not found]     ` <BANLkTi=uvN8_u6SQhKfs2BwOnSOCQApKSQ@mail.gmail.com>
2011-05-11  3:42       ` Khem Raj
2011-05-10 15:58 ` Koen Kooi
2011-05-11  9:45   ` Richard Purdie
2011-05-11 10:13     ` Koen Kooi
2011-05-11 10:54       ` Richard Purdie [this message]
2011-05-11 11:45         ` Koen Kooi
2011-05-15 21:31           ` Khem Raj
2011-05-15 20:22     ` Khem Raj
2011-05-15 21:34       ` Khem Raj
2011-05-11 13:30 ` Richard Purdie
2011-05-15 20:27   ` Otavio Salvador
2011-05-16 12:24     ` 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=1305111264.30391.338.camel@rex \
    --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