Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] multiple architectures
Date: Wed, 30 Sep 2009 09:01:02 +0200	[thread overview]
Message-ID: <20090930090102.0189852d@surf> (raw)
In-Reply-To: <20090930062658.GG25852@moomers.org>

Le Wed, 30 Sep 2009 01:26:58 -0500,
Igor Serebryany <igor47@moomers.org> a ?crit :

> 	I need both an x86 and an amd64 version of my buildroot
> filesystem and kernel. I've been making this happen by a very
> inefficient process - keeping two copies of the buildroot source (one
> for each arch), making local/projectname an svn working copy, making
> all changes to the x86 version and using 'svn update' to merge changes
> 	back into the amd64 version.
> 
> 	I'm sure there must be a better way. How do people on here
> manage maintaining identical builds for multiple architectures? 

Use out-of-tree compilation with O=, with two different configurations
files.

Say ~/buildroot contains your Buildroot source code :

 * Store your x86 configuration in ~/buildroot/config.x86 and your
   x86_64 configuration in ~/buildroot/config.x86_64

 * To run the x86 compilation, do :

    cd ~/buildroot/
    cp config.x86 .config
    make O=~/buildroot-x86

 * To run the x86_64 compilation, do :

    cd ~/buildroot/
    cp config.x86_64 .config
    make O=~/buildroot-x86_64

Of course, when you make a change to one of the .config, make sure that
you update the corresponding config.{x86,x86_64}.

Do that solves your problem ?

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090930/bf48a650/attachment.pgp>

  reply	other threads:[~2009-09-30  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  6:26 [Buildroot] multiple architectures Igor Serebryany
2009-09-30  7:01 ` Thomas Petazzoni [this message]
2009-09-30  7:26   ` Igor Serebryany
2009-09-30  8:13   ` Bjørn Forsman
2009-09-30  8:31     ` Thomas Petazzoni
2009-09-30  9:08       ` Peter Korsgaard
2009-09-30 10:20       ` Bjørn Forsman
2009-09-30 11:44         ` Peter Korsgaard

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=20090930090102.0189852d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox