All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: linaro-dev@lists.linaro.org,
	 openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: Riku Voipio <riku.voipio@linaro.org>,
	Hope Michael <michael.hope@linaro.org>,
	Matthew Gretton-Dann <matthew.gretton-dann@linaro.org>
Subject: New layout for OpenEmbedded layers
Date: Wed, 05 Dec 2012 12:03:03 +0100	[thread overview]
Message-ID: <50BF29E7.5080203@linaro.org> (raw)

Hello

Now at Linaro we have two layers for our OpenEmbedded work:

- meta-aarch64
- meta-linaro

First one contains everything we need to get AArch64 booted in
fastmodels: toolchain, kernel and few recipes which needed changes to
build for AArch64. I am working on merging those changes into main
OpenEmbedded layers.

Second one is gcc-linaro from Toolchain WG and some recipes and changes
from Platform team.

Those who do OE builds with our toolchain have some components changed
due to our metadata (like Busybox with dpkg-deb) and I decided to fix it.

Today I pushed "new-layout" branch of meta-linaro repository. It
contains all Linaro layers:

- meta-aarch64
- meta-linaro
- meta-linaro-toolchain

First one was merged from meta-aarch64 repository and moved to own
directory. Third one contains only toolchain bits. Second one has all
that left.

I have to do some test builds with this layout and once they will
confirm that it works I will change all CI builds. This will also
deprecate meta-aarch64 repository - it will not have any updates and
will be dropped in ~month.

Opinions?



                 reply	other threads:[~2012-12-05 11:18 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=50BF29E7.5080203@linaro.org \
    --to=marcin.juszkiewicz@linaro.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=matthew.gretton-dann@linaro.org \
    --cc=michael.hope@linaro.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=riku.voipio@linaro.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.