From: Igor Serebryany <igor47@moomers.org>
To: buildroot@busybox.net
Subject: [Buildroot] multiple architectures
Date: Wed, 30 Sep 2009 01:26:58 -0500 [thread overview]
Message-ID: <20090930062658.GG25852@moomers.org> (raw)
Hi!
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?
--Igor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090930/58eede28/attachment.pgp>
next reply other threads:[~2009-09-30 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 6:26 Igor Serebryany [this message]
2009-09-30 7:01 ` [Buildroot] multiple architectures Thomas Petazzoni
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=20090930062658.GG25852@moomers.org \
--to=igor47@moomers.org \
--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