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

Chris Larson clarson at kergoth.com
Thu Nov 22 23:11:35 UTC 2012


On Thu, Nov 22, 2012 at 4:10 PM, Chris Larson <clarson at kergoth.com> wrote:

> Yeah, that quick script just ran bitbake -e, not bitbake -e <provider>.
> You could modify it easily enough to support that, though.
>
> 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 '^#')
>

Oh, I forgot to mention that it can handle filtering not just regular
variables, but functions as well, since it's in python:

    bitbake-env base_set_filespath
-- 
Christopher Larson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20121122/0fd27d17/attachment-0001.html>


More information about the bitbake-devel mailing list