From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: core-image-rt building a lot more packages than expected
Date: Fri, 12 Aug 2011 17:55:52 +0100 [thread overview]
Message-ID: <1313168152.14274.517.camel@rex> (raw)
In-Reply-To: <4E455483.6020602@linux.intel.com>
On Fri, 2011-08-12 at 09:27 -0700, Darren Hart wrote:
> I have been surprised over the last few days at the number of packages
> being built for the core-image-rt target, which for reference is as follows:
>
> #
> # Copyright (C) 2010 Intel Corporation.
> #
>
> DESCRIPTION = "Real-Time Linux Image"
> DEPENDS = "linux-yocto-rt"
>
> require recipes-core/images/core-image-minimal.bb
>
> IMAGE_INSTALL += "rt-tests"
>
> LICENSE = "MIT"
>
>
> The only dependencies of rt-tests are:
>
> DEPENDS = "linux-libc-headers eglibc"
>
>
> Building core-image-rt schedules 3154 tasks, and among them are things like:
> lttng-viewer
> gst-plugins-base (bad, good, etc)
> gtk+
> libogg
> libtheora
> owl-video
> clutter
> libglade
> librsvg
> mesa-demos
> x11-perf
> xvideo-tests
> etc etc etc
>
> I noticed my local.conf contains:
> EXTRA_IMAGE_FEATURES = "tools-debug tools-profile tools-testapps
> debug-tweaks"
>
> That hasn't changed in a while, but perhaps those features now pull in
> more than they used to? Or if they don't, are we unintentionally pulling
> in a lot more packages for what is essentially a minimal image?
If you enable those things they do get pulled into images and some of
the dependency chains are pretty heavy. They are no longer default in
local.conf though.
Cheers,
Richard
prev parent reply other threads:[~2011-08-12 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 16:27 core-image-rt building a lot more packages than expected Darren Hart
2011-08-12 16:55 ` 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=1313168152.14274.517.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--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.