[OE-core] [PATCH 0/6] RFC Distro config changes

Khem Raj raj.khem at gmail.com
Sun May 15 20:22:31 UTC 2011


On Wed, May 11, 2011 at 2:45 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> 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 at 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"
>

this wont work. Since virtclasses empty out some of these vars e.g. native
resets STAGING_DIR_HOST but this will still append -uclibc to it since append
happens at the end


> 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
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




More information about the Openembedded-core mailing list