From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/6] support/gnuconfig: update README.buildroot with reality
Date: Tue, 28 May 2019 22:34:12 +0200 [thread overview]
Message-ID: <20190528203416.32261-3-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20190528203416.32261-1-thomas.petazzoni@bootlin.com>
4 out of 5 packages who are not using autotools but needed their
gnuconfig files updated were not complying with the recommandation in
support/gnuconfig/README.buildroot. The fifth package was converted to
be like the others: use UPDATE_CONFIG_HOOK as a <pkg>_POST_PATCH_HOOKS
rather than calling the CONFIG_UPDATE macro directly.
Now that all packages are consistent, update the README.buildroot file
to match the reality.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
support/gnuconfig/README.buildroot | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/support/gnuconfig/README.buildroot b/support/gnuconfig/README.buildroot
index a71ed93010..7ba2a332a4 100644
--- a/support/gnuconfig/README.buildroot
+++ b/support/gnuconfig/README.buildroot
@@ -10,7 +10,7 @@ If for some reason your package does not use the autotools-package
infrastructure, you can request the config.guess and/or config.sub
files of your package to be updated by using:
- $(call CONFIG_UPDATE,directory-of-your-package-sources)
+<pkg>_POST_PATCH_HOOKS += UPDATE_CONFIG_HOOK
--- UPDATE ---
GNU config is now managed in git, so to update:
--
2.21.0
next prev parent reply other threads:[~2019-05-28 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:34 [Buildroot] [PATCH v2 0/6] gnuconfig and csky updates Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 1/6] package/lmbench: use UPDATE_CONFIG_HOOK instead of CONFIG_UPDATE Thomas Petazzoni
2019-05-30 10:33 ` Peter Korsgaard
2019-05-28 20:34 ` Thomas Petazzoni [this message]
2019-05-30 10:34 ` [Buildroot] [PATCH v2 2/6] support/gnuconfig: update README.buildroot with reality Peter Korsgaard
2019-05-28 20:34 ` [Buildroot] [PATCH v2 3/6] support/gnuconfig: update to 2019-05-28 Thomas Petazzoni
2019-05-30 10:36 ` Peter Korsgaard
2019-05-30 12:38 ` Thomas Petazzoni
2019-05-30 12:53 ` Peter Korsgaard
2019-05-31 12:57 ` Thomas Petazzoni
2019-05-31 21:02 ` Peter Korsgaard
2019-05-31 20:04 ` Yann E. MORIN
2019-05-31 21:02 ` Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 4/6] toolchain/toolchain-external/toolchain-external-csky: new package Thomas Petazzoni
2019-05-29 5:48 ` Guo Ren
2019-05-29 6:49 ` Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 5/6] configs/csky_gx6605s: use the C-SKY external toolchain package Thomas Petazzoni
2019-05-28 20:34 ` [Buildroot] [PATCH v2 6/6] support/config-fragments/autobuild: add testing for the C-SKY architecture Thomas Petazzoni
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=20190528203416.32261-3-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--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.