From: Scott Rifenbark Date: Mon, 18 Jul 2016 17:21:06 +0000 (-0700) Subject: ref-manual: Applied review comments to logging mechanism section X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=818e439cf5d23a3b0a2b89cd79acfa97929d983b;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git ref-manual: Applied review comments to logging mechanism section Fixes [YOCTO #9950] I Provided a suggested introductory sentence and a better link to the logging.class file, which is near the end. (From yocto-docs rev: 6f296266b35f17792510d6a01f5640ba30818a22) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index f94e3a79ffb..40e39b55785 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml @@ -356,8 +356,8 @@
Recipe Logging Mechanisms - Best practices exist while writing recipes that both log build - progress and act on build conditions such as warnings and errors. + The Yocto Project provides several logging functions for producing + debugging output and reporting errors and warnings. For Python functions, the following logging functions exist. All of these functions log to ${T}/log.do_task, @@ -411,13 +411,13 @@ bbplain, bbnote, bbdebug, bbwarn, bberror, and bbfatal. - - - - For guidance on how logging is handled in both Python and Bash recipes, see the - logging.bbclass file in the + The + logging + class implements these functions. + See that class in the meta/classes folder of the - Source Directory. + Source Directory + for information.