public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: David Wuertele <dave@crossplex.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH 2 of 2] docs: Add strategies for assembling root filesystems
Date: Thu, 17 Nov 2011 20:15:00 -0000	[thread overview]
Message-ID: <CAJaQfj3yWbT26Futh-G23qi8AGoaSs6j+H781TUr849kM1bUJQ@mail.gmail.com> (raw)
In-Reply-To: <20111117202859.4c07bbfc@skate>

Thomas, this is why I created Crossplex.  It is a library of make
macros that let you specify arbitrary numbers of glibc or uclibc
toolchain configurations and target filesystem configurations, and it
is designed from the ground up to support efficient rebuilding and
parallel building.  It has recipes for many different popular
packages.

It is still a work in progress, but Motorola (and another large
company I'm not allowed to mention) are using it to build some of
their products.

I keep the github repo (https://github.com/wuertele/crossplex) more up
to date than the website (crossplex.org).

Dave Wuertele

On Thu, Nov 17, 2011 at 11:28 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Thu, 17 Nov 2011 00:29:27 +0100,
> "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> a écrit :
>
>> > Expand the documentation for using a crosstool-NG-generated
>> > toolchain for building a root filesystem for a target device.
>>
>> Not much to say, I wrote much of it! :-)
>> But still, a few comments below...
>
> I think this part of the documentation should point to existing
> embedded Linux build systems, which already do this job, with several
> advantages :
>
>  * Well-tested and proven packages for the most common open-source
>   components needed in embedded Linux systems
>
>  * Cross-compilation issues that arise with the most common packages
>   are already fixed by those build systems. For example, try to
>   cross-compile Python. It is basically impossible without heavily
>   patching its build system. Which is already done by OpenEmbedded,
>   Buildroot, OpenBricks and all those projects.
>
>  * The build process is reproducible. I have encountered way too many
>   embedded Linux systems built manually, for which nobody knows the
>   build procedure and nobody is capable of replacing a given component
>   by a newer version of that component to fix a bug.
>
> To me, suggesting people to manually create their root filesystem is a
> strong mistake.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-11-17 20:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 22:46 [PATCH 0 of 2] documentation update Trevor Woerner
2011-11-16 22:46 ` [PATCH 1 of 2] docs: --target versus --host Trevor Woerner
2011-11-16 23:18   ` Yann E. MORIN
2011-11-16 23:24     ` Trevor Woerner
2011-11-17 19:26     ` Thomas Petazzoni
2011-11-17 21:56       ` Trevor Woerner
2011-11-16 22:46 ` [PATCH 2 of 2] docs: Add strategies for assembling root filesystems Trevor Woerner
2011-11-16 23:29   ` Yann E. MORIN
2011-11-17 19:29     ` Thomas Petazzoni
2011-11-17 20:15       ` David Wuertele [this message]
2011-11-17 20:32         ` Thomas Petazzoni
2011-11-17 23:05       ` Trevor Woerner

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=CAJaQfj3yWbT26Futh-G23qi8AGoaSs6j+H781TUr849kM1bUJQ@mail.gmail.com \
    --to=dave@crossplex.org \
    --cc=crossgcc@sourceware.org \
    --cc=thomas.petazzoni@free-electrons.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).