All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded Core - Ready for extended users
Date: Mon, 16 May 2011 17:49:42 +0100	[thread overview]
Message-ID: <1305564582.2429.90.camel@phil-desktop> (raw)
In-Reply-To: <BANLkTimSNvdsc1BoCk4ofNh4-nFuO5bg2A@mail.gmail.com>

On Mon, 2011-05-16 at 14:52 +0200, Frans Meulenbroeks wrote:
> I think the community could benefit if you add info (a pointer) in this
> thread
> - how to set up a build environment
> - policies on what goes into oe-core and meta-oe and what not (and how to
> deal with things that do not go into it)
> - a migration scenario from the current repo to the new structure (what are
> we doing with the existing recipes)
> - how to add new distro's and bsp's
> 
> I know some (if not all) info has been sent around over time, but I feel it
> would help if this announcement would carry the info to get people started
> (and/or point to a web page that has the above info).

Yes, agreed, I think that would be useful.  The build environment setup
is certainly a bit different to "classic" oe and it took me a while to
figure it out.  At the time there didn't seem to be much documentation
on how that stuff was meant to work, though with hindsight I now suspect
the Poky manual might have been the place to look.

p.





  reply	other threads:[~2011-05-16 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 11:26 OpenEmbedded Core - Ready for extended users Richard Purdie
2011-05-16 11:57 ` Koen Kooi
2011-05-16 12:52 ` Frans Meulenbroeks
2011-05-16 16:49   ` Phil Blundell [this message]
2011-05-17  6:23     ` Anders Darander
2011-05-17  6:38       ` Koen Kooi
2011-05-17  7:04         ` Anders Darander
2011-05-17  9:25           ` Petr Štetiar
2011-05-17 19:49             ` Richard Purdie
2011-05-19  6:12               ` Anders Darander

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=1305564582.2429.90.camel@phil-desktop \
    --to=philb@gnu.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.