From: "Linus Walleij" <linus.ml.walleij@gmail.com>
To: linux-embedded@vger.kernel.org, r.schwebel@pengutronix.de
Subject: Re: building Rootfs
Date: Mon, 7 Jul 2008 22:34:11 +0200 [thread overview]
Message-ID: <63386a3d0807071334q2242ac45x540cee2a3fcb231b@mail.gmail.com> (raw)
In-Reply-To: <20080707181018.GG4319@pengutronix.de>
OK Robert wrote this on ARM-Linux mailinglist but the discussion
belongs on linux-embedded, so I'm moving it there, the suggested
ptxdist ML seems inapropriate for the entire embedded
community.
2008/7/7 Robert Schwebel <r.schwebel@pengutronix.de>:
> On Mon, Jul 07, 2008 at 06:01:51PM +0800, Eric Miao wrote:
>> or start from buildroot, scratchbox and openembedded as a tool, you've
>> really got a lot to learn :-)
>
> Or ptxdist, or course :-)
Robert, can you brief us of how ptxdist fits together with
OpenEmbedded? What does these two projects actually
share? Where do they do similar things in parallel for
example?
I'm trying - real hard - to get an idea of how people out
there prefer to build their root filesystems in cross-compiled
environments.
Rob Landley recently wrote up a small blurb on why native
compilation is the way to go, and a small roadmap on how
he intended to get there using e.g. Qemu and Firmware Linux,
c.f: http://www.landley.net/code/firmware/about.html
which finally won me over to that line of thinking.
Debian and friends obviously go this way now.
However, when it comes to the widespread and much
fragmented ways of cross-compiling a rootfs, including the
stuff put together by MontaVista, WR and all those animals
in the forest, obviously based on RPM (build systems I
haven't put my hands inside, since they are proprietary)
there seems to be very little consensus. ptxdist stands out
but do you get a lot of outside contributions for it? As it
looks it seems you're running it yourself. (Beware: I
haven't looked close.)
What else is there out there for rootfs, really? A hack
from every embedded company there is? I'm more after
what people actually *use* and what is community driven
here, not so much opinions on what is best (which will
probably be the unwanted side effect of this mail
anyway...)
Linus
next parent reply other threads:[~2008-07-07 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY131-W252EE4B85EEB3F7A87466FE2940@phx.gbl>
[not found] ` <4871E98F.8030802@gmail.com>
[not found] ` <20080707181018.GG4319@pengutronix.de>
2008-07-07 20:34 ` Linus Walleij [this message]
2008-07-07 21:21 ` building Rootfs Robert Schwebel
2008-07-09 0:14 ` Linus Walleij
2008-07-09 7:06 ` Robert Schwebel
2008-07-07 23:24 ` Haller, John H (John)
2008-07-08 6:54 ` Robert Schwebel
2008-07-08 14:00 ` Wolfgang Denk
2008-07-08 23:53 ` Linus Walleij
2008-07-09 0:52 ` David VomLehn
2008-07-09 7:10 ` Robert Schwebel
2008-07-09 6:21 ` Wolfgang Denk
2008-07-09 6:43 ` Robert Schwebel
2008-07-09 7:22 ` Peter Korsgaard
2008-07-09 8:22 ` Marek Skuczynski
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=63386a3d0807071334q2242ac45x540cee2a3fcb231b@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).