From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: linaro-dev@lists.linaro.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: ATTENTION: OpenEmbedded layers from Linaro have new structure
Date: Wed, 13 Mar 2013 15:45:46 +0100 [thread overview]
Message-ID: <5140911A.90604@linaro.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
Today I made several changes to OpenEmbedded layers hosted on
git.linaro.org:
- - meta-aarch64
- - meta-linaro
Meta-aarch64 is now empty and is obsolete. Probably will be removed from
server in about month or two.
Meta-linaro repository got new structure based on meta-openembedded one
and contains three layers:
- - meta-aarch64
- - meta-linaro
- - meta-linaro-toolchain
Today meta-aarch64 is just a copy of old one but everything not related
to ARMv8 will be moved from it to meta-linaro.
Meta-linaro-toolchain contains just gcc-linaro and support for external
Linaro cross toolchains (armv7a and armv8 ones).
I considered creation of meta-aarch64-arm-toolchain one with ARM Ltd.
version of gcc but it is not often used option so can stay where it is
now (meta-aarch64).
Instructions how to start building for ARMv8 (with OE) are in wiki:
https://wiki.linaro.org/HowTo/ARMv8/OpenEmbedded
Note that any scripts present in 'meta-aarch64' got dropped. If you want
easy way then use 'jenkins-setup' scripts like it is described in wiki.
They are written to be as easy to use as possible.
If you have any problems/questions: reply to this email.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJRQJERAAoJECbKqQEReiUeKFgQAMUYDB1ymQs8ZspWVynJVJMQ
InFsFQUd/QZCgNB9GcG6IepzmViHeMlIxNQ7u+KFABGV8uAz8gwdgcPtWwa/dc1b
wu8u84mmwy77WBIMuX087AiXdg8WhJDJz5sztBoK2PL8Ljn1TFB/R17Ew90eN3zn
o1DpPnbgMGs67phNiTy8GiQxyaaLZub0ZZZ5v00tWdt7x4vazw6n2r8/o+wzGLj2
536KI13Sepso2dg2mrpqzrwVH8KFP7S/rRiDdKI4Gw9FlTPiaiEEadX7OPKx8YC5
j1WIR0u66LCSe+F3NsfNfEgTOXPGVUNgqvemwGYXQuOLUKz7nnnkEdVRUegSuEVj
+bZsgzFunghOsvEgX4ynxLVXgOrkiH4PPMhD+OWcB1pso9+ZdVFTVO2oGOnDg9pK
ov7lidEoUDDIZqHxjy5cV36jDnXt8BTI9uEIjVo9gH/0g/67QImXHVONcppg2MfM
GDfhYorkah3VTo9zgHZKCDEIstT1OsCSg+PNeKCAN6fDUdmnzGxCJNEj2CaRAzaI
vJekxAK0+ptscJ9c+bUmAtcBK+XRvJ9K3naN+apUm13Y6INwKuS68knWzOJc0xhd
rpPQ2EcYd8FP1gspjNJPyQKWr2pAUGQkOGkhHrsrb4nj6mkMDDgZ2ET1x8uxI056
vMRn7PKF7x3bItUP9NzA
=GNf7
-----END PGP SIGNATURE-----
reply other threads:[~2013-03-13 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5140911A.90604@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--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.