From: Khem Raj <raj.khem@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Yocto Project <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: RFC: User configurable recipe features
Date: Wed, 12 Oct 2011 12:32:28 -0700 [thread overview]
Message-ID: <4E95EB4C.5060408@gmail.com> (raw)
In-Reply-To: <5A638733-1EF0-4FF9-96D9-61702DEE2FBC@dominion.thruhere.net>
On 10/12/2011 12:30 PM, Koen Kooi wrote:
>
> Op 12 okt. 2011, om 20:44 heeft Khem Raj het volgende geschreven:
>
>> On 10/12/2011 8:55 AM, Darren Hart wrote:
>>> Hi Tim,
>>>
>>> On 10/11/2011 04:49 PM, Tim Bird wrote:
>>>> On 10/10/2011 11:41 AM, Darren Hart wrote:
>>>>> As part of working on meta-tiny, I've come across a need (want?) to
>>>>> present users with the ability to select some set of features in a local
>>>>> configuration file that will impact the build of the image and a set of
>>>>> recipes.
>>>>
>>>> Can you tell me more about meta-tiny? this is the first I've heard
>>>> about this (sorry if discussion went by on the mailing list and I
>>>> missed it), and I'm very interested.
>>>
>>>
>>> Tim,
>>>
>>> I'll be presenting things in more detail at ELCE, Friday @ 3:45 PM in
>>> the Kepler room. The summary is that I have received a lot of questions
>>> along the lines of "How small of an image can I build with Yocto?".
>>
>> I guess yocto needs to define another profile(distro) to really demonstrate how small it can get. There are other distros based on oe-core e.g. micro and even slugos where the image sizes are really small slugos/uclibc image is around 2.7M eglibc based image is 3.5M
>
> And don't forget angstrom, that scales all the way down to an fbdev gui fit inside 80kiB.
indeed.
next prev parent reply other threads:[~2011-10-12 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 18:41 RFC: User configurable recipe features Darren Hart
2011-10-11 15:53 ` McClintock Matthew-B29882
2011-10-11 16:06 ` Darren Hart
2011-10-11 22:15 ` Richard Purdie
2011-10-11 23:51 ` Khem Raj
2011-10-12 0:18 ` Philip Balister
2011-10-12 15:41 ` Darren Hart
2011-10-12 15:47 ` Koen Kooi
2011-10-12 15:52 ` Paul Eggleton
2011-10-12 16:49 ` Darren Hart
2011-10-12 15:40 ` Darren Hart
2011-10-11 23:49 ` Tim Bird
2011-10-12 15:55 ` Darren Hart
2011-10-12 18:44 ` Khem Raj
2011-10-12 19:30 ` Koen Kooi
2011-10-12 19:32 ` Khem Raj [this message]
2011-10-12 20:15 ` Darren Hart
2011-10-12 19:13 ` Tim Bird
2011-10-12 16:59 ` Darren Hart
2011-10-12 17:19 ` Tim Bird
2011-10-12 19:22 ` William Mills
2011-10-13 8:30 ` Jack Mitchell
2011-10-13 18:33 ` William Mills
2011-10-13 20:50 ` Khem Raj
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=4E95EB4C.5060408@gmail.com \
--to=raj.khem@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=yocto@yoctoproject.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.