From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Multiple architectures best practices?
Date: Sat, 20 Feb 2010 20:07:35 +0100 [thread overview]
Message-ID: <20100220200735.495486b5@surf> (raw)
In-Reply-To: <BLU148-W126CE5F8A30A9DD8A9BAA5EB7A0@phx.gbl>
Hello Terry,
On Tue, 29 Dec 2009 14:44:51 -0500
Terry Forrest <zippybot7@hotmail.com> wrote:
> Hi All - new to buildroot and am impressed! Nice design
> and implementation.
Thanks!
> We would like to use BR to build for two architectures from
> the same tree. We can use a local x86 for a "simulation" mode,
> and the target is arm. I see that this is cleanly supported in the
> 2009.11 release.
>
> My question is on a "best practice" for this. I've set up
> a top-level Makefile that goes something like this:
> This seems to work okay - any comments or warnings?
> Again, I'm new to BR and want to make sure I'm not
> gonna step in anything.
Your Makefile looks good to me.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-02-20 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 19:44 [Buildroot] Multiple architectures best practices? Terry Forrest
2010-02-20 19:07 ` 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=20100220200735.495486b5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.