On Thu, May 26, 2011 at 4:24 PM, Richard Purdie <[email protected]> wrote: > On Thu, 2011-05-26 at 14:12 -0700, Darren Hart wrote: >> Note: I used bb.note() instead of bb.debug() to ensure the message at least >> makes it to the console. From what I could gather, bb.debug() doesn't >> go anywhere during recipe parsing. > > Why? > > We exclude about 30 different recipes when parsing and would you really > want to see a usability message from each one when you likely don't care > about it? > > A bb.debug is fine and the user can see it if they run with -D to get > more info. A bb.note is just irritating.
As alternative, *If* there's a need for a one time message when building, which is questionable, and assuming the variable is configuration, not recipe bound, one could always install a ConfigParsed event handler and warn if e.g. UBOOT_ENTRYPOINT or UBOOT_LOADADDRESS are set and UBOOT_MACHINE is not. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
