[OE-core] what's the easiest way to see the difference some local configuration makes?

[Andrei Gherzan]

On Jul 7, 2012 7:14 PM, "Robert P. J. Day" <rpjday at crashcourse.ca> wrote:
>
> On Sat, 7 Jul 2012, Saul Wold wrote:
>
> > 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!
>
>    oh, that's already on my list, i was just trying to dig up
> clever(?) ways to show *only* what would change.

If you don't know what would change just save bitbake -e before and after
changes and meld / diff.

@g
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120708/d171023a/attachment-0002.html>