Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Added menu entry to build squashfs host tools separately
Date: Mon, 3 Feb 2014 08:10:41 +0100	[thread overview]
Message-ID: <20140203081041.12e92a72@skate> (raw)
In-Reply-To: <52EE8618.7040708@mind.be>

Dear Arnout Vandecappelle,

On Sun, 02 Feb 2014 18:53:28 +0100, Arnout Vandecappelle wrote:

> > In the other filesystems, we do not necessarily select
> > BR2_PACKAGE_HOST_<utilities to build the filesystem>, and therefore we
> > keep the <pkg>_DEPENDENCIES that contains host-<utilities to build the
> > filesystem>.
> 
>   I would actually prefer to have both the select and the dependencies, 
> since that's what we do for target packages.

But then we should be consistent and do this all over the place: as
soon as a host package has a Config.in symbol, then it should be
selected by its reverse dependencies.

>   In addition (but that's just a small consideration), if at some point 
> we make TARGETS contain only the target targets (heh), then the 
> dependency chain for filesystems is still correct.

Hum, there are some host packages that we want to build and that are
not dependencies of target packages. That's the very reason why we have
the "Host utilities" menu.

That being said, it would certainly be good to have two make variables:

 * TARGET_PACKAGES
 * HOST_PACKAGES

that are respectively used to contain the list of targets for
enabled target packages, and the list of targets for enabled host
packages.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-03  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 13:52 [Buildroot] [PATCH] Added menu entry to build squashfs host tools separately Jeroen De Wachter
2014-01-31  8:22 ` Thomas Petazzoni
2014-02-02 17:53   ` Arnout Vandecappelle
2014-02-03  7:10     ` Thomas Petazzoni [this message]
2014-02-04 23:26       ` Arnout Vandecappelle
2014-02-03 11:26 ` Yann E. MORIN
2014-02-03 18:56   ` Jeroen De Wachter

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=20140203081041.12e92a72@skate \
    --to=thomas.petazzoni@free-electrons.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