From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] base: make feature backfilling happen earlier
Date: Tue, 29 Jan 2013 12:07:28 +0100 [thread overview]
Message-ID: <ly4ni0z1qn.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <97105828.GXrr1zfWsR@helios> (Paul Eggleton's message of "Mon, 28 Jan 2013 16:34:40 +0000")
Paul Eggleton <paul.eggleton@linux.intel.com> writes:
>> >> 1. set some defaults on distribution base ...
>> >> 2. allow to override these defaults on a per-project base
fwiw, I am using now
_EXT_PROJECT_FEATURES = "\
largefile nfsroot modules ld-is-gold ${PROJECT_FEATURES} \
${DISTRO_FEATURES_INITMAN} ${DISTRO_FEATURES_LIBC} \
${@base_contains('PROJECT_FEATURES', 'alsa', 'sound', '', d)} \
${@base_contains('PROJECT_FEATURES', 'directfb', 'screen', '', d)} \
...
DISTRO_FEATURES = "${@' '.join(sorted(list( \
set(d.getVar('_EXT_PROJECT_FEATURES', True).split()) - \
set(d.getVar('NO_PROJECT_FEATURES', True).split()))))}"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "${DISTRO_FEATURES_BACKFILL}"
Enrico
next prev parent reply other threads:[~2013-01-29 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 17:52 [PATCH 0/2] DISTRO_FEATURES compatibility fixes Ross Burton
2013-01-24 17:52 ` [PATCH 1/2] bitbake.conf: unbreak all builds with custom DISTRO_FEATURES Ross Burton
2013-01-24 17:52 ` [PATCH 2/2] base: make feature backfilling happen earlier Ross Burton
2013-01-25 18:06 ` Enrico Scholz
2013-01-28 12:54 ` Richard Purdie
2013-01-28 13:55 ` Enrico Scholz
2013-01-28 14:19 ` Paul Eggleton
2013-01-28 14:52 ` Enrico Scholz
2013-01-28 15:00 ` Phil Blundell
2013-01-28 15:44 ` Enrico Scholz
2013-01-28 15:58 ` Paul Eggleton
2013-01-28 16:23 ` Enrico Scholz
2013-01-28 16:34 ` Paul Eggleton
2013-01-29 11:07 ` Enrico Scholz [this message]
2013-01-28 16:15 ` Phil Blundell
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=ly4ni0z1qn.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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