From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Creating Rootfs images without packages
Date: Wed, 12 Oct 2011 06:34:04 -0600 [thread overview]
Message-ID: <4E95893C.6050903@mlbassoc.com> (raw)
In-Reply-To: <CAObi9r9=55i4W686VfCv-TGSChsrewu7zSGUsPZC2PbA3x3zbQ@mail.gmail.com>
On 2011-10-12 06:22, mgundes wrote:
> Hi,
>
> I think one of the big issue with OE is build time. It does everything
> for you, so that it takes too much times. I want to minimize build time and
> realized that OE creates ipkgs for almost every package. If there is a way
Not true. Only the packages needed to complete your image will be built.
That said, there are some packages which are built (the first time only) that
comprise the build environment and tool chain which takes a lot of time, but
this is only the first time through.
What image & target are you building for and what packages are built that you
don't think needed to be built?
> to prevent creation of ipkgs it would be really good for me. In my opinion,
> it would be fine for other people too since usually rootfs directory is
> enough and ipkgs are not frequently used directly by developers.
>
> I have asked in freenode oe room but friends said there no way to do that
> in OE system. If there is no way to do that in current OE, do you plan to
> add as a feature?
>
> Thanks,
>
> Regards
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-10-12 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 12:22 Creating Rootfs images without packages mgundes
2011-10-12 12:34 ` Gary Thomas [this message]
2011-10-12 13:10 ` mgundes
2011-10-12 13:21 ` Gary Thomas
2011-10-12 13:47 ` mgundes
2011-10-12 15:29 ` Chris Larson
2011-10-12 20:46 ` dashesy
2011-10-12 20:50 ` Khem Raj
2011-10-13 7:30 ` mgundes
2011-10-13 0:37 ` Ulf Samuelsson
2011-10-13 7:22 ` mgundes
2011-10-13 9:26 ` Phil Blundell
2011-10-13 11:07 ` mgundes
2011-10-14 0:05 ` 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=4E95893C.6050903@mlbassoc.com \
--to=gary@mlbassoc.com \
--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.