From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: what's the easiest way to see the difference some local configuration makes?
Date: Sat, 07 Jul 2012 09:06:47 -0700 [thread overview]
Message-ID: <4FF85E97.9010202@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207071126550.20571@oneiric>
On 07/07/2012 08:43 AM, Robert P. J. Day wrote:
>
> i recall that there's a current request to be able to list the
> packages and versions that relate *just* to the current target and
> machine, so i'm looking for any other way to do this so students can
> see the difference for themselves.
>
> for example, i'm starting with a configuration of "qemuarm", and i
> can do a fetchall:
>
> $ bitbake -c fetchall core-image-minimal
>
> and let that run. so far, so good -- i've now fetched everything
> required for this target. if i repeat that command, obviously,
> nothing should change, and it doesn't. (i don't even have to build
> the target, i'm just doing fetching for now.)
>
> now let's say i add to my local.conf:
>
> IMAGE_INSTALL_append = " strace"
>
> i suspect there's an easier way to see this, but if i want to *prove*
> that the strace recipe would be part of the build, i can do:
>
> $ bitbake -c fetchall -n core-image-minimal [dry run]
>
Have you tried bitbake -e which prints out all the variables and python
functions, you can then grep for ^IMAGE_INSTALL or what ever you expect
to affect by your change
Sau!
> to get:
>
> ... snip ...
> NOTE: Running task 302 of 309 (ID: 21, /home/rpjday/oe/oe-core/meta/recipes-devtools/strace/strace_4.7.bb, do_fetch)
> NOTE: Running task 309 of 309 (ID: 1, /home/rpjday/oe/oe-core/meta/recipes-core/images/core-image-minimal.bb, do_fetchall)
> NOTE: Tasks Summary: Attempted 309 tasks of which 307 didn't need to be rerun and all succeeded.
> $
>
> so that's "proof" that i've officially added strace to my
> core-image-minimal.
>
> i'm sure that's massive overkill -- is there a simpler way to
> demonstrate this? i want to start simple by adding a single package,
> then move on to adding multiple packages, and features and so on, and
> let the student see the effect of each change.
>
> what's the easiest way to do that? thanks.
>
> rday
>
next prev parent reply other threads:[~2012-07-07 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 15:43 what's the easiest way to see the difference some local configuration makes? Robert P. J. Day
2012-07-07 16:06 ` Saul Wold [this message]
2012-07-07 16:13 ` Robert P. J. Day
2012-07-08 9:57 ` Andrei Gherzan
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=4FF85E97.9010202@linux.intel.com \
--to=sgw@linux.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