From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] meta-skeleton: Add busybox config fragment example
Date: Tue, 13 Aug 2013 09:44:56 -0700 [thread overview]
Message-ID: <1376412296-7521-2-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1376412296-7521-1-git-send-email-sgw@linux.intel.com>
This shows an example of the config fragment support that
both the linux-yocto and busybox recipes use. This example
is specific to busybox.
By adding busybox CONFIG options into a .cfg file and then
adding that .cfg file to SRC_URI the merge_config.sh script will
correctly handle these CONFIG options during the do_configure task.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg | 1 +
meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
2 files changed, 6 insertions(+)
create mode 100644 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
create mode 100644 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
new file mode 100644
index 0000000..42c6730
--- /dev/null
+++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
@@ -0,0 +1 @@
+CONFIG_RFKILL=n
diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
new file mode 100644
index 0000000..641f04a4
--- /dev/null
+++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
@@ -0,0 +1,5 @@
+FILESEXTRAPATHS := "${THISDIR}/${PN}"
+
+SRC_URI += " \
+ file://no_rfkill.cfg \
+ "
--
1.8.1.4
next prev parent reply other threads:[~2013-08-13 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:44 [PATCH 1/2] meta-skeleton: layer.conf should also have .bbappend in BBFILES Saul Wold
2013-08-13 16:44 ` Saul Wold [this message]
2013-08-13 17:18 ` [PATCH 2/2] meta-skeleton: Add busybox config fragment example Darren Hart
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=1376412296-7521-2-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--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 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.