From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Which OE branch for beagleboard?
Date: Sat, 31 Jul 2010 11:50:17 +0200 [thread overview]
Message-ID: <i30rks$8aq$2@dough.gmane.org> (raw)
In-Reply-To: <9D2EA12D-A6C9-4965-A833-3B6CDCD8CD7B@mac.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31-07-10 11:46, Elvis Dowson wrote:
> Hi,
> Which OE branch should I use to build angstrom images for the beagleboard?
Use http://gitorious.org/angstrom/angstrom-setup-scripts [1], that will
setup the right branch and bitbake for you.
regards,
Koen
[1] once gitorious comes back to life, you can get the script from the
webinterface as well
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMU/HZMkyGM64RGpERAjLSAJ9FbjrMRyG+INGFTmpVoprde42TiQCdFFwr
OZYJNFtAYGr4l4TVv466UOo=
=HhyF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-31 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 9:46 Which OE branch for beagleboard? Elvis Dowson
2010-07-31 9:50 ` Koen Kooi [this message]
2010-07-31 10:58 ` Elvis Dowson
2010-07-31 12:08 ` Koen Kooi
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='i30rks$8aq$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox