Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] make host-cryptopp selectable
Date: Thu, 20 Dec 2018 21:22:47 -0200	[thread overview]
Message-ID: <20181220232249.29434-1-casantos@datacom.com.br> (raw)

Quoting Thomas Petazzoni, 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.

Carlos Santos (2):
  package/cryptopp: add a blind Config.in.host
  package/tegrarcm: select host-cryptopp

 package/Config.in.host          | 1 +
 package/cryptopp/Config.in.host | 6 ++++++
 package/tegrarcm/Config.in.host | 1 +
 3 files changed, 8 insertions(+)
 create mode 100644 package/cryptopp/Config.in.host

-- 
2.19.2

             reply	other threads:[~2018-12-20 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 23:22 Carlos Santos [this message]
2018-12-20 23:22 ` [Buildroot] [PATCH v2 1/2] package/cryptopp: add a blind Config.in.host Carlos Santos
2018-12-20 23:22 ` [Buildroot] [PATCH v2 2/2] package/tegrarcm: select host-cryptopp Carlos Santos

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=20181220232249.29434-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