From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host
Date: Sun, 23 Dec 2018 15:19:48 -0200 [thread overview]
Message-ID: <20181223171950.3979-1-casantos@datacom.com.br> (raw)
The plan for the future is:
* All host packages have a Config.in.host option.
* The host packages that are only build dependencies of other packages
have a blind Config.in.host option
* The host packages that are useful by themselves continue to have a
visible Config.in.host option.
host-waf gets a blind Config.in.host, because it exists only to build
Waf-based packages that set <PKG>_NEEDS_EXTERNAL_WAF to YES.
A help text is included to document the package, only, since it is not
shown in the configuration menu.
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
Changes v1->v2:
- Explain the motivation in the commit message
- Make the Config.in.host blind
Changes v2->v3:
- Removes "quoting Thomas Petazzoni" from the commit messege, since
it's not a personal opinion but a consensus among project members.
---
package/Config.in.host | 1 +
package/waf/Config.in.host | 6 ++++++
2 files changed, 7 insertions(+)
create mode 100644 package/waf/Config.in.host
diff --git a/package/Config.in.host b/package/Config.in.host
index 16b474fc9d..3644436fe3 100644
--- a/package/Config.in.host
+++ b/package/Config.in.host
@@ -64,6 +64,7 @@ menu "Host utilities"
source "package/uboot-tools/Config.in.host"
source "package/util-linux/Config.in.host"
source "package/vboot-utils/Config.in.host"
+ source "package/waf/Config.in.host"
source "package/xorriso/Config.in.host"
source "package/zip/Config.in.host"
source "package/zstd/Config.in.host"
diff --git a/package/waf/Config.in.host b/package/waf/Config.in.host
new file mode 100644
index 0000000000..81a5c5cc27
--- /dev/null
+++ b/package/waf/Config.in.host
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_HOST_WAF
+ bool
+ help
+ WAF, the meta build system
+
+ https://waf.io/
--
2.20.1
next reply other threads:[~2018-12-23 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 17:19 Carlos Santos [this message]
2018-12-23 17:19 ` [Buildroot] [PATCH v3 2/3] doc/manual: document the waf packages may need to select host-waf Carlos Santos
2018-12-26 21:31 ` Thomas Petazzoni
2018-12-23 17:19 ` [Buildroot] [PATCH v3 3/3] package/mpv: selec host-waf Carlos Santos
2018-12-26 21:30 ` [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host Thomas Petazzoni
2018-12-26 21:55 ` Yann E. MORIN
2019-01-03 21:50 ` Thomas Petazzoni
2019-01-03 22:06 ` Yann E. MORIN
2019-01-03 22:14 ` Yann E. MORIN
2019-01-03 23:34 ` Carlos Santos
2019-01-04 8:58 ` Thomas Petazzoni
2019-01-04 10:05 ` Carlos Santos
2019-01-04 10:10 ` Thomas Petazzoni
2019-01-04 11:06 ` Arnout Vandecappelle
2019-01-04 11:51 ` Yann E. MORIN
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=20181223171950.3979-1-casantos@datacom.com.br \
--to=casantos@datacom.com.br \
--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