Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] use host compressor for rootfs
Date: Sun, 6 Apr 2014 12:46:19 +0300	[thread overview]
Message-ID: <20140406094619.GE4096@tarshish> (raw)
In-Reply-To: <20140406113248.5d7216a6@skate>

Hi Thomas, Thomas,

On Sun, Apr 06, 2014 at 11:32:48AM +0200, Thomas Petazzoni wrote:
> On Sun, 6 Apr 2014 10:25:24 +0100 (BST), Philippe Reynes wrote:
> 
> > I've missed this "mandatory dependancy".
> > I suppose that this dependancy is usefull to uncompress tarball.
> > But I think that the compilation of firmware should be done with
> > tools compiled by buildroot.
> > 
> > If lzma is used to compress the rootfs, then lzma is compile
> > by builtoot. If gzip is used to compress the rootfs, then we use
> > local gzip. It's not very "coherent".
> > And using compiled binary with buildroot increase chance to
> > regenerate firmware on (very) different machine.
> > 
> > And I agree with you, it's not a "real" issue, it's more a "nice to have".
> 
> Well, I guess there are two important things here:
> 
>  1) Buildroot tries to avoid building native utilities needlessly. So
>     when possible, we try to use the tools available on the machine, in
>     order to keep the overall build time as reasonable as possible.
> 
>  2) gzip and bzip2 are widely available tools, which haven't caused any
>     compatibility issue in years. On the other hands, tools like lzma,
>     xz and so on are a lot less widely available. They may not even be
>     available at all on old Linux distributions that some companies are
>     still using.
> 
> Both of these points combined explain why we handle gzip/bzip2
> differently than lzma/xz.

Since commit d1f325f554cab (xzcat: treat as host prerequisite and build if 
needed) xz is always built when the host does not have it. Can we remove 
host-xz from the dependencies of HOST_SQUASHFS and ROOTFS_*_XZ?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-04-06  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06  7:48 [Buildroot] [PATCH 0/2] use host compressor for rootfs Philippe Reynes
2014-04-06  7:48 ` [Buildroot] [PATCH 1/2] rootfs-gzip: use host-gzip instead of local gzip Philippe Reynes
2014-04-06  7:48 ` [Buildroot] [PATCH 2/2] rootfs-bzip: use host-bzip2 instead of local bzip2 Philippe Reynes
2014-04-06  7:59 ` [Buildroot] [PATCH 0/2] use host compressor for rootfs Baruch Siach
2014-04-06  9:25   ` Philippe Reynes
2014-04-06  9:31     ` Thomas De Schampheleire
2014-04-06  9:59       ` Philippe Reynes
2014-04-06  9:32     ` Thomas Petazzoni
2014-04-06  9:46       ` Baruch Siach [this message]
2014-04-12 16:43 ` 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=20140406094619.GE4096@tarshish \
    --to=baruch@tkos.co.il \
    --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