Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example
Date: Tue, 13 Aug 2013 12:26:52 -0500	[thread overview]
Message-ID: <520A6C5C.3050308@windriver.com> (raw)
In-Reply-To: <1376413879-9809-1-git-send-email-sgw@linux.intel.com>

On 8/13/13 12:11 PM, Saul Wold wrote:
> 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.
>
> v2: fixed FILESEXTRAPATHS
>
> 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

Should be "# CONFIG_RFKILL is not set", I believe the =n will work, but it 
doesn't following the kconfig conventions.

--Mark

> 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_prepend := "${THISDIR}/${PN}:"
> +
> +SRC_URI += " \
> +	    file://no_rfkill.cfg \
> +           "
>



  parent reply	other threads:[~2013-08-13 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 17:11 [PATCH 2/2 v2] meta-skeleton: Add busybox config fragment example Saul Wold
2013-08-13 17:23 ` Laszlo Papp
2013-08-13 17:23   ` Laszlo Papp
2013-08-13 17:33     ` Mark Hatle
2013-08-13 17:40       ` Laszlo Papp
2013-08-13 17:58         ` Mark Hatle
2013-08-13 18:02           ` Bruce Ashfield
2013-08-13 17:26 ` Mark Hatle [this message]
2013-08-13 17:40   ` Darren Hart
2013-08-13 17:46   ` Saul Wold
2013-08-13 18:39 ` Otavio Salvador

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=520A6C5C.3050308@windriver.com \
    --to=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox