All of 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:36:07 +0200	[thread overview]
Message-ID: <20160830103607.0607237b@jenova> (raw)
In-Reply-To: <20160830101545.19fee5f8@jenova>

Sorry for the noise, I should have waited a little longer before asking
this question.

On Tue, 30 Aug 2016 10:15:45 +0200
Manuel Gro? <mgr@nordkrater.de> wrote:

> 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.

I got confused about those patches, sorry. There is no patch for the
merge_config.sh whatsoever.
 
> Now to my question(s):
> Am I supposed to apply these patches outside buildroot, or is there
> another, proper way to patch the script?

Since there is no patch for the merge-script, and the other ones are
already applied, this question solves itself.

> Am I breaking anything by patching the script?

I obviously would break the 'pkg-kconfig' package, which uses this
script for other packages. I also imagine kernel builds using fragments
would suffer from this.
-- 
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/76eb2238/attachment.asc>

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  8:15 [Buildroot] Question regarding support/kconfig Manuel Groß
2016-08-30  8:36 ` Manuel Groß [this message]
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=20160830103607.0607237b@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 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.