All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building for multiple machines
Date: Mon, 11 Oct 2010 09:47:32 +0200	[thread overview]
Message-ID: <i8ufek$27r$2@dough.gmane.org> (raw)
In-Reply-To: <AANLkTin8xbEBR=mVr3PHN9cjwqtUoM9BxpYkgBE7p_UY@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-10-10 08:27, Frans Meulenbroeks wrote:
> 2010/10/11 Elvis Dowson <elvis.dowson@mac.com>:
>> Hi,
>>        What should I do build for multiple machines ?
>>
>> I have an overo-oe repository, but I need to temporarily build u-boot for a different board.
>>
>> In my auto.conf, the entry is MACHINE="overo"
>>
>> u-boot board definitions for say beagleboard, have named the board "beagle"
>>
>> So, would an appropriate command be
>>
>> bitbake u-boot-omap3 MACHINE="beagle"
>>
>>
>> Elvis Dowson
> 
> I guess trying this would ahve been much faster than waiting for an answer here.
> 
> And OE does not have an auto.conf

OE *does* have an auto.conf, pretty much since the start:

koen@dominion:/OE/org.openembedded.dev/conf$ git blame bitbake.conf |
grep auto.conf
00f6a165 (Chris Larson 2004-12-09 01:08:40 +0000 695) include conf/auto.conf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMssEUMkyGM64RGpERAqxMAJ9ORcv5iii/70qi6c7EC7ReXlKSQgCgm4UF
qgXeKzlpaIRCTrylt4wM+hU=
=eNId
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-10-11  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  5:59 Building for multiple machines Elvis Dowson
2010-10-11  6:27 ` Frans Meulenbroeks
2010-10-11  7:47   ` Koen Kooi [this message]
2010-10-11  7:57     ` Elvis Dowson
2010-10-11 11:23       ` Frans Meulenbroeks
2010-10-11  8:09     ` Frans Meulenbroeks

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='i8ufek$27r$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.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 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.