[bitbake-devel] how easy to extend "bitbake -e" to print *selected* subset of variables?

Robert P. J. Day rpjday at crashcourse.ca
Fri Nov 23 00:03:08 UTC 2012


On Thu, 22 Nov 2012, Chris Larson wrote:

> Yeah, that quick script just ran bitbake -e, not bitbake -e
> <provider>. You could modify it easily enough to support that,
> though.

  hang on ... i actually did just that to search the output of:

$ bitbake -e linux-omap4

but i still don't see a number of variables i'm interested in, and i'm
not sure how to do that.

> You could also try out https://gist.github.com/4133101. It's just a
> quick prototype. Drop it next to bitbake in bitbake/bin/. It fixes a
> couple minor annoyances with bitbake -e and it sends all the bitbake
> log output from stdout to stderr, so you can redirect that
> independently of the emitted variables and values.
>
> Usage examples:
>
>     bitbake-env DISTRO MACHINE do_configure
>     bitbake-env -r virtual/kernel FILE
>     eval $(bitbake-env TMPDIR | grep -v '^#')

  ok, i'll check that out, thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


More information about the bitbake-devel mailing list