* what's the easiest way to see the difference some local configuration makes?
@ 2012-07-07 15:43 Robert P. J. Day
2012-07-07 16:06 ` Saul Wold
0 siblings, 1 reply; 4+ messages in thread
From: Robert P. J. Day @ 2012-07-07 15:43 UTC (permalink / raw)
To: OE Core mailing list
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]
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
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what's the easiest way to see the difference some local configuration makes?
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
2012-07-07 16:13 ` Robert P. J. Day
0 siblings, 1 reply; 4+ messages in thread
From: Saul Wold @ 2012-07-07 16:06 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what's the easiest way to see the difference some local configuration makes?
2012-07-07 16:06 ` Saul Wold
@ 2012-07-07 16:13 ` Robert P. J. Day
2012-07-08 9:57 ` Andrei Gherzan
0 siblings, 1 reply; 4+ messages in thread
From: Robert P. J. Day @ 2012-07-07 16:13 UTC (permalink / raw)
To: Saul Wold; +Cc: Patches and discussions about the oe-core layer
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.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what's the easiest way to see the difference some local configuration makes?
2012-07-07 16:13 ` Robert P. J. Day
@ 2012-07-08 9:57 ` Andrei Gherzan
0 siblings, 0 replies; 4+ messages in thread
From: Andrei Gherzan @ 2012-07-08 9:57 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
On Jul 7, 2012 7:14 PM, "Robert P. J. Day" <rpjday@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
[-- Attachment #2: Type: text/html, Size: 2229 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-07-08 10:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2012-07-07 16:13 ` Robert P. J. Day
2012-07-08 9:57 ` Andrei Gherzan
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.