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 2/2] package/tegrarcm: select host-cryptopp and drop BR2_arm dependency
Date: Thu, 13 Dec 2018 20:58:36 +0100	[thread overview]
Message-ID: <20181213205836.29997ef4@windsurf> (raw)
In-Reply-To: <794738414.2421573.1544608748810.JavaMail.zimbra@datacom.com.br>

Hello Carlos,

On Wed, 12 Dec 2018 07:59:08 -0200 (BRST), Carlos Santos wrote:

> > Of course we can't do it all in one big shot, but still it should probably be
> > approached in a somewhat more structured way. For example, when we add a
> > Config.in.host for a package, we also (perhaps in a separate commit) add the
> > select statements for it in all packages that depend on it.
> > 
> > 
> > Also note that the idea was to make these Config.in.host options blind (i.e.
> > promptless).  
> 
> Make sense if the host package exists only to support building another
> package (that selects and depends on it) but there are other reasons
> why a host package may be necessary, e.g. I need host-mtools for a
> post-image script.

Yes, of course, we want *some* host packages to be visible in
menuconfig.

Basically, the current situation is:

 * Most host packages don't have any Config.in.host options (blind or
   visible), because they are merely build dependencies of other
   packages.

 * A few host packages do have a visible Config.in.host because they
   are useful by themselves, and not just as a build dependency of
   something else: image generation tools, flashing tools, qemu, etc.

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.

Does that clarify where we want to go ?

Best regards,

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

      reply	other threads:[~2018-12-13 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  2:56 [Buildroot] [PATCH 1/2] package/cryptopp: add Config.in.host Carlos Santos
2018-12-12  2:56 ` [Buildroot] [PATCH 2/2] package/tegrarcm: select host-cryptopp and drop BR2_arm dependency Carlos Santos
2018-12-12  8:46   ` Thomas Petazzoni
2018-12-12  9:04     ` Arnout Vandecappelle
2018-12-12  9:59       ` Carlos Santos
2018-12-13 19:58         ` Thomas Petazzoni [this message]

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=20181213205836.29997ef4@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