From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Bringing an image from OE to OE-Core
Date: Tue, 04 Oct 2011 21:27:56 +0100 [thread overview]
Message-ID: <1317760084.14671.99.camel@ted> (raw)
In-Reply-To: <4E8B6564.4090002@balister.org>
On Tue, 2011-10-04 at 15:58 -0400, Philip Balister wrote:
> I'm about to start bringing some images I use from OE to OE-core. The
> first issue I saw is there is no task-proper-tools in oe-core (where
> oe-core means the set of layers created by the Angstrom setup scripts).
>
> Should I add task-proper-tools to meta-oe, or is there a better way to
> add a full features set of tools to an image? Basically, the image is
> more desktop like than embedded.
The core-image-lsb is the OE-Core image with the full fat tools
included. I'd suggest starting from that and see what is missing.
I'd also note we have IMAGE_FEATURES which you can add tools-sdk to
which may or may not include more of what you want (basically a
development toolchain+tools).
CHeers,
Richard
prev parent reply other threads:[~2011-10-04 20:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 19:58 Bringing an image from OE to OE-Core Philip Balister
2011-10-04 20:08 ` Saul Wold
2011-10-04 20:27 ` Philip Balister
2011-10-04 20:32 ` Saul Wold
2011-10-04 22:43 ` Mark Hatle
2011-10-05 14:14 ` Philip Balister
2011-10-05 14:47 ` Eric Bénard
2011-10-05 15:49 ` Mark Hatle
2011-10-05 16:20 ` Koen Kooi
2011-10-05 21:07 ` Philip Balister
2011-10-05 16:39 ` Eric Bénard
2011-10-05 19:35 ` Khem Raj
2011-10-05 20:03 ` Philip Balister
2011-10-05 20:18 ` Joshua Lock
2011-10-05 20:24 ` Khem Raj
2011-10-05 22:51 ` Saul Wold
2011-10-07 5:51 ` Frans Meulenbroeks
2011-10-04 20:15 ` Khem Raj
2011-10-04 20:27 ` Richard Purdie [this message]
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=1317760084.14671.99.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.