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

[Robert P. J. Day]

On Thu, 22 Nov 2012, Chris Larson wrote:

>
>
> On Thu, Nov 22, 2012 at 5:03 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
>       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.
>
> What variables are you not seeing? bitbake -e shows all variables
> but ones which are flagged 'unexport' (e.g. DISTRO, MACHINE). --

  *sigh* ... just ignore my stupidity.  in my fatigue, i totally
forgot that configuring a pandaboard required adding meta-ti on top of
straight OE, and there was no yocto-related content involved, but i
was still remembering all of the variables i could see when i was
using yocto.

 in any event, i like the bitbake-env script, is it worth adding some
variant of that to bitbake itself?

rday

-- 

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

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