| Message ID | 20181221002221.16024-1-casantos@datacom.com.br |
|---|---|
| State | Superseded, archived |
| Headers | show |
| Series | [v2,1/2] package/waf: add a blind Config.in.host | expand |
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/
Quoting Thomas Petazzoni, the idea we have 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 --- package/Config.in.host | 1 + package/waf/Config.in.host | 6 ++++++ 2 files changed, 7 insertions(+) create mode 100644 package/waf/Config.in.host