[yocto] ref manual, sections 2.3.[67], ambiguity with "-b" option to bitbake

[Rifenbark, Scott M]

Robert, 

I think section 2.3.7 cut corners when it said "If you want to show the environment resulting from parsing a single recipe, use the -b reciename form."  My guess is that it should say ".... use the -b <somepath/somefile.bb>."

Someone on the maillist correct me if this is a bad assumption.

Scott

>-----Original Message-----
>From: yocto-bounces at yoctoproject.org [mailto:yocto-
>bounces at yoctoproject.org] On Behalf Of Robert P. J. Day
>Sent: Tuesday, November 05, 2013 1:05 AM
>To: Yocto discussion list
>Subject: [yocto] ref manual, sections 2.3.[67], ambiguity with "-b" option to
>bitbake
>
>
>  section 2.3.6 of ref manual explains that bitbake "-b" option refers specifically
>to a recipe *file*:
>
>"If you really want to build a specific .bb file, you can use the command form
>bitbake -b <somepath/somefile.bb>."
>
>but the very next section uses "-b" in the context of a simple recipe
>*name* when combining it with "-e":
>
>"You can use the -e BitBake option to display the resulting environment for a
>configuration when you do not specify a package or for a specific package
>when you do specify the package. If you want to show the environment
>resulting from parsing a single recipe, use the -b recipename form."
>
>  that suggests i could run something like:
>
>$ bitbake -e -b zlib
>
>which seems to work. clarification? is "-b" meant to refer to a simple recipe
>*name* when used in the context of "-e"?
>
>rday
>
>--
>
>===========================================================
>=============
>Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                        http://crashcourse.ca
>
>Twitter:                                       http://twitter.com/rpjday
>LinkedIn:                               http://ca.linkedin.com/in/rpjday
>===========================================================
>=============
>_______________________________________________
>yocto mailing list
>yocto at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto