This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2 of 2] docs: Add strategies for assembling root filesystems


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]