Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] [RFC] package/pkg-waf.mk: mimic selection of host-waf
Date: Fri, 21 Dec 2018 16:34:30 +0100	[thread overview]
Message-ID: <20181221163430.56a34588@windsurf> (raw)
In-Reply-To: <20181221002221.16024-2-casantos@datacom.com.br>

Hello,

On Thu, 20 Dec 2018 22:22:21 -0200, Carlos Santos wrote:
> Since host-waf's Config.in.host is blind, it is not possible to select
> it in the configuration menu. There are two possible solutions for this
> problem:
> 
> - Add "select BR2_PACKAGE_HOST_WAF" to package/mpv/Config.in (currently
>   only mpv requires host-waf). Also, document that BR2_PACKAGE_HOST_WAF
>   must be selected when <PKG>_NEEDS_EXTERNAL_WAF is YES.
> 
> - Set BR2_PACKAGE_HOST_WAF to 'y' in the waf-package macro. This one is
>   simpler because it does not require changing anything else.
> 
> Signed-off-by: Carlos Santos <casantos@datacom.com.br>

I understand the idea that doing this avoids repeating a "select
BR2_PACKAGE_HOST_WAF" in all packages using host-waf. However, I don't
think we want to go down the route of setting those variables from the
make logic. I don't have a very strong argument to defend this
position, but to me it looks more logical that we continue to use
kconfig-level "select" to enable those config options.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-21 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21  0:22 [Buildroot] [PATCH v2 1/2] package/waf: add a blind Config.in.host Carlos Santos
2018-12-21  0:22 ` [Buildroot] [PATCH v2 2/2] [RFC] package/pkg-waf.mk: mimic selection of host-waf Carlos Santos
2018-12-21 15:34   ` Thomas Petazzoni [this message]
2018-12-21 16:04     ` Carlos Santos
2018-12-21 19:48       ` 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=20181221163430.56a34588@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox