From: Igor Serebryany <igor47@moomers.org>
To: buildroot@busybox.net
Subject: [Buildroot] multiple architectures
Date: Wed, 30 Sep 2009 02:26:29 -0500 [thread overview]
Message-ID: <20090930072629.GH25852@moomers.org> (raw)
In-Reply-To: <20090930090102.0189852d@surf>
On Wed, Sep 30, 2009 at 09:01:02AM +0200, Thomas Petazzoni wrote:
> Of course, when you make a change to one of the .config, make sure that
> you update the corresponding config.{x86,x86_64}.
This is the problem that I've been using svn to solve, by
* running 'make saveconfig',
* committing the resulting local/myproject directory to a repository
* running 'svn update' in another local/myproject64 directory that
points at the same repository but the working copy has been customized for
64bit architecture.
svn update then merges the config changes, leaving the local
modifications (especially to the kernel .config) in place.
i was hoping there was some kind of magical make flag that would use the
same config files but do some kind of 'oh edit it for this other
architecture' magic.
--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/6f0db4ca/attachment.pgp>
next prev parent reply other threads:[~2009-09-30 7:26 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
2009-09-30 7:26 ` Igor Serebryany [this message]
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=20090930072629.GH25852@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