Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 2 v3] xzcat: treat as host prerequisite and build if needed
Date: Sat, 07 Sep 2013 08:11:00 +0200	[thread overview]
Message-ID: <8761ud17rf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <a7969409ab53a2fc00c4.1375434315@BEANTN0L019720> (Thomas De Schampheleire's message of "Fri, 02 Aug 2013 11:05:15 +0200")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:

 Thomas> If xzcat is not present on the host system, buildroot bails out early asking
 Thomas> the developer to install it (xzcat is now a DL_TOOLS_DEPENDENCY)
 Thomas> Conversely, when BR2_TARGET_ROOTFS_CPIO_XZ is enabled, then host-xz is a
 Thomas> build dependency, and no manual action is required from the developer.

 Thomas> Because the second approach is nicer, also build host-xz when xzcat is not
 Thomas> available, using the host-prerequisite and suitable-host-pkg mechanisms,
 Thomas> already used for tar.

 Thomas> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

 Thomas> ---
 Thomas> v3: update after $(firstword) change
 Thomas> v2: avoid filtering out xzcat from DL_TOOLS_DEPENDENCIES (comment ThomasP)

Committed, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2013-09-07  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  9:05 [Buildroot] [PATCH 0 of 2 v3] Introduce suitable-extractor and add host-xzcat dependency Thomas De Schampheleire
2013-08-02  9:05 ` [Buildroot] [PATCH 1 of 2 v3] infra: introduce suitable-extractor helper function Thomas De Schampheleire
2013-08-17 19:59   ` Thomas De Schampheleire
2013-08-27 13:05     ` Thomas De Schampheleire
2013-09-07  6:09   ` Peter Korsgaard
2013-08-02  9:05 ` [Buildroot] [PATCH 2 of 2 v3] xzcat: treat as host prerequisite and build if needed Thomas De Schampheleire
2013-09-07  6:11   ` Peter Korsgaard [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=8761ud17rf.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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