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 10:45:17 +0100 [thread overview]
Message-ID: <1305107117.30391.325.camel@rex> (raw)
In-Reply-To: <4B81AF14-3B09-4B77-884C-AAF3BE237FA9@dominion.thruhere.net>
On Tue, 2011-05-10 at 17:58 +0200, Koen Kooi wrote:
> Op 10 mei 2011, om 16:00 heeft Richard Purdie het volgende geschreven:
>
> > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> > As discussed, we want to make OE-Core usable with no distro set. This patch series
> > makes some big steps towards that goal. I'd be interested in feedback on whether it
> > does the right things and would be usable by others.
> >
> > The key is the inclusion of a distro/defaultsetup.conf file by bitbake.conf and
> > in turn this pulls in a variety of other common include files which can likely be
> > shared. Any point of this cycle can be overridden by another layer so its totally
> > customisable. I'd encourage users to use the pieces they can where possible so we
> > all share best practises but obviously people have choice.
> >
> > I did dump a load of "default" variables into default-distrovars.inc, I'm not
> > calling that file finished, I just had to draw the line somewhere and start a
> > discussion about this :)
>
> For angstrom we had to change a few things, have a look at
> http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/tree/conf/distro/include/angstrom-core-tweaks.inc , specifically lines 12-18 and 53-54
I don't understand what TOOLCHAIN_PATH and TOOLCHAIN_SYSPATH do, I can't
find any reference to them in OECore. 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.
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.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-11 9:48 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 1/6] Drop poky-floating-revisions.inc, poky-bleeding.conf and poky-lsb.conf 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 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: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 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: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 [this message]
2011-05-11 10:13 ` Koen Kooi
2011-05-11 10:54 ` Richard Purdie
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=1305107117.30391.325.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