From: Darren Hart <dvhart@linux.intel.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Do we have a package that installs the kernel headers and config into the target?
Date: Fri, 06 Apr 2012 09:07:44 -0700 [thread overview]
Message-ID: <4F7F14D0.1060408@linux.intel.com> (raw)
In-Reply-To: <A25F549E4D43CD42B4C02DF47A1913230FCFD897@SHSMSX102.ccr.corp.intel.com>
On 04/06/2012 04:12 AM, Cui, Dexuan wrote:
> Cui, Dexuan wrote on 2012-04-06:
>> Darren Hart wrote on 2012-04-06:
>>> On 04/05/2012 09:41 PM, Cui, Dexuan wrote:
>>> While I understand there are valid use cases, I think this is generally
>>> contrary to workflow of the project. We build the OS, it runs on the
>>> target. This is building a general purpose OS, and then having it build
>>> itself out more. It doesn't feel like an embedded workflow.
> BTW, my question might be simplified as:
> If we strictly follow the rule the target OS shouldn't build itself out
> more, why do we supply a recipe core-image-sato-sdk.bb that can
> create an image with tools-sdk that includes development tools
> like gcc? :-)
>
> Or, while we recommend the common embedded workflow, we
> also somewhat support (or tolerate) the way "the target builds
> itself out more"?
>
Yup, agree.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-04-06 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 3:20 Do we have a package that installs the kernel headers and config into the target? Cui, Dexuan
2012-04-06 3:55 ` Darren Hart
2012-04-06 4:41 ` Cui, Dexuan
2012-04-06 6:07 ` Darren Hart
2012-04-06 7:48 ` Cui, Dexuan
2012-04-06 11:12 ` Cui, Dexuan
2012-04-06 16:07 ` Darren Hart [this message]
2012-04-06 14:11 ` Steve Sakoman
2012-04-06 16:23 ` Darren Hart
2012-04-09 6:43 ` Cui, Dexuan
-- strict thread matches above, loose matches on Subject: below --
2012-04-06 18:03 Daniel Lazzari
2012-04-09 6:48 ` Cui, Dexuan
2012-04-09 9:10 ` Maksym Parkachov
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=4F7F14D0.1060408@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=dexuan.cui@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox