From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: crossgcc@sourceware.org
Subject: Re: --host versus --target
Date: Thu, 17 Nov 2011 19:23:00 -0000 [thread overview]
Message-ID: <20111117202255.24636416@skate> (raw)
In-Reply-To: <CAHUNapQ2OiWoOhYtH76zfbb2MOP2jSOrbpyToHCifPApr4suEA@mail.gmail.com>
Le Wed, 16 Nov 2011 11:16:08 -0500,
Trevor Woerner <twoerner@gmail.com> a écrit :
> I wasn't aware there existed different strategies for putting together
> a cross-root-filesystem, I'm quite happy you took the time to list
> them. Ironically, looking through the list (and I realize you're not
> going to agree) I think option #1 is the best. Having recently put in
> the time to put together such an image, I can attest it was quite a
> pain getting the various packages to compile correctly.
That's because you shouldn't be doing that manually. There are embedded
Linux build systems that are designed to precisely handle this work.
OpenEmbedded, Yocto, Buildroot, PTXdist, OpenBricks, etc. My preference
of course goes towards Buildroot, since I'm part of the development
team. But the others are fine, too, since they make this
cross-compilation easier *and* reproducible.
Handling the cross-compilation of the various packages for its embedded
Linux system in a manual way is a very bad development practice, in my
opinion.
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
prev parent reply other threads:[~2011-11-17 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 21:52 Trevor Woerner
2011-11-15 22:45 ` Michael Hope
2011-11-15 22:49 ` Yann E. MORIN
2011-11-16 16:16 ` Trevor Woerner
2011-11-16 18:13 ` Yann E. MORIN
2011-11-16 20:18 ` Trevor Woerner
2011-11-16 22:43 ` Yann E. MORIN
2011-11-17 19:23 ` Thomas Petazzoni [this message]
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=20111117202255.24636416@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=crossgcc@sourceware.org \
/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).