Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Manuel Groß" <mgr@nordkrater.de>
To: buildroot@busybox.net
Subject: [Buildroot] Question regarding support/kconfig
Date: Tue, 30 Aug 2016 10:15:45 +0200	[thread overview]
Message-ID: <20160830101545.19fee5f8@jenova> (raw)

Hello everyone,

I am failing to find some documentation or explanatory commit-message
on this topic, so I hope I'll gain some insight here.
If there is any existing documentation on this, I'll happily accept
pointers :)

I want to use the support/kconfig/merge_config.sh script outside
buildroot to merge buildroot config fragments. To do so, I need the
script to recognise options beginning with 'BR2_' instead of 'CONFIG_'.
I noticed a patch for the script lying around
(patches/01-kconfig-kernel-to-buildroot.patch), which contains exactly
those modifications.

Now to my question(s):
Am I supposed to apply these patches outside buildroot, or is there
another, proper way to patch the script? Am I breaking anything by
patching the script?
-- 
Gr??e/Regards
Manuel Gro?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160830/c69527e5/attachment.asc>

             reply	other threads:[~2016-08-30  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  8:15 Manuel Groß [this message]
2016-08-30  8:36 ` [Buildroot] Question regarding support/kconfig Manuel Groß
2016-08-30 19:44   ` Arnout Vandecappelle

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=20160830101545.19fee5f8@jenova \
    --to=mgr@nordkrater.de \
    --cc=buildroot@busybox.net \
    /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