From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: handling of machine/distro features stuff
Date: Fri, 24 Nov 2006 17:03:26 +0100 [thread overview]
Message-ID: <200611241703.26332.openembedded@hrw.one.pl> (raw)
In-Reply-To: <1163755540.5551.4.camel@localhost.localdomain>
Dnia piątek, 17 listopada 2006 10:25, Richard Purdie napisał:
> > Which points me to this idea: how about adding COMBINED_FEATURES into
> > overrides? I do not know will it slow down BitBake or make metadata
> > bit more ugly but it is kind of solution.
> Also, this would automatically make any package machine specific and
> make multimachine pointless (anything using COMBINED_FEATURES is machine
> specific).
Koen suggested other solution - marking packages MACHINE specific when
COMBINED_FEATURES are used. For example wpa-supplicant will get this:
DEPENDS = "gnutls ${@base_contains('COMBINED_FEATURES', 'pci', 'madwifi-ng', '',d)}"
PACKAGE_ARCH = "${@base_contains('COMBINED_FEATURES', 'pci', ${MACHINE}, ${TARGET_ARCH}, d)}"
export HAS_PCI = ${@base_contains('COMBINED_FEATURES', 'pci', 1, 0,d)}
do_configure () {
install -m 0755 ${WORKDIR}/defconfig-gnutls .config
if [ "x$HAS_PCI" == "x1" ] then; do
echo "CONFIG_DRIVER_MADWIFI=y" >> .config
echo "CFLAGS += -I${STAGING_INCDIR}/madwifi-ng" >> .config
fi
}
Opinions?
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
"To be or not to be that is the question.":
every programmer knows the answer $2b or (not $2b) is $ff.
next prev parent reply other threads:[~2006-11-24 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 14:28 RFC: handling of machine/distro features stuff Marcin Juszkiewicz
2006-10-29 22:10 ` Jamie Lenehan
2006-10-30 1:32 ` Justin Patrin
2006-11-04 13:37 ` Leon Woestenberg
2006-11-17 0:01 ` Marcin Juszkiewicz
2006-11-17 9:25 ` Richard Purdie
2006-11-24 16:03 ` Marcin Juszkiewicz [this message]
2006-11-24 17:56 ` 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=200611241703.26332.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.