From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] JFFS2 / MTD suggestions
Date: Wed, 8 Apr 2009 07:50:04 -0700 [thread overview]
Message-ID: <20090408075004.18784e45@surf> (raw)
In-Reply-To: <878wmc2y8c.fsf@macbook.be.48ers.dk>
Le Tue, 07 Apr 2009 19:02:43 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Or even better, compile lzo for the host and link against that.
I know that's what we do for automake, autoconf, pkg-config, m4 and a
bunch of other stuff. But I must admit, that personnaly, I'm not
really a fan of this. I would rather prefer to leverage what's
installed on the host, and consider that Buildroot having dependencies
on installed packages (liblzo-dev and others) is normal.
Currently, one of the strong advantage of Buildroot compared to more
heavyweight solutions like OpenEmbedded is that the time for Buildroot
checkout to the first basic root filesystem being produced is very
small (15 minutes or so). If we start compiling more and more host
tools to the point that we basically recompile everything that's on the
host, we'll to some extent loose this advantage.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-04-08 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 15:35 [Buildroot] JFFS2 / MTD suggestions Thomas Petazzoni
2009-04-07 15:57 ` Lloyd Sargent
2009-04-08 13:02 ` Peter Korsgaard
2009-04-07 16:58 ` Cyril HAENEL
2009-04-07 17:13 ` Peter Korsgaard
2009-04-09 8:07 ` Cyril HAENEL
2009-04-09 9:34 ` Peter Korsgaard
2009-04-07 17:02 ` Peter Korsgaard
2009-04-08 14:50 ` Thomas Petazzoni [this message]
2009-04-08 14:59 ` Peter Korsgaard
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=20090408075004.18784e45@surf \
--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