<div dir="ltr"><div><div><div>Hi!<br><br></div>I did my best to follow <a href="https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded">patch submission guidelines</a> and <a href="https://www.openembedded.org/wiki/Styleguide">code styleguide</a> but this is my very first patch to anything in the Yocto project. Please let me know if and how I can improve future patch submissions! I figured since it's my first time, I would follow up and say hello :)<br><br></div>This patch addresses <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=9962">bug 9962</a> by updating the documentation of bitbake's -v and -D CLI options. I copied the updated text directly from the bug report, and changed it both in the code and in the user manual.<br><br></div>Anyway hi! I hope to contribute more soon :)<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 21, 2017 at 1:27 PM, Diana Thayer <span dir="ltr"><<a href="mailto:garbados@gmail.com" target="_blank">garbados@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Per bug-9962, expanded and clarified documentation<br>
for -v, --verbose and -D, --debug.<br>
<br>
Signed-off-by: Diana Thayer <<a href="mailto:garbados@gmail.com">garbados@gmail.com</a>><br>
---<br>
doc/bitbake-user-manual/<wbr>bitbake-user-manual-intro.xml | 16 +++++++++++++---<br>
lib/bb/main.py | 15 +++++++++++++--<br>
2 files changed, 26 insertions(+), 5 deletions(-)<br>
<br>
diff --git a/doc/bitbake-user-manual/<wbr>bitbake-user-manual-intro.xml b/doc/bitbake-user-manual/<wbr>bitbake-user-manual-intro.xml<br>
index 7248a0b..5bbfc67 100644<br>
--- a/doc/bitbake-user-manual/<wbr>bitbake-user-manual-intro.xml<br>
+++ b/doc/bitbake-user-manual/<wbr>bitbake-user-manual-intro.xml<br>
@@ -504,9 +504,19 @@<br>
Read the specified file before bitbake.conf.<br>
-R POSTFILE, --postread=POSTFILE<br>
Read the specified file after bitbake.conf.<br>
- -v, --verbose Output more log message data to the terminal.<br>
- -D, --debug Increase the debug level. You can specify this more<br>
- than once.<br>
+ -v, --verbose Enable tracing of shell tasks (with 'set -x').<br>
+ Also print bb.note(...) messages to stdout (in<br>
+ addition to writing them to ${T}/log.do_<task>).<br>
+ -D, --debug Increase the debug level. You can specify this<br>
+ more than once. -D sets the debug level to 1,<br>
+ where only bb.debug(1, ...) messages are printed<br>
+ to stdout; -DD sets the debug level to 2, where<br>
+ both bb.debug(1, ...) and bb.debug(2, ...)<br>
+ messages are printed; etc. Without -D, no debug<br>
+ messages are printed. Note that -D only affects<br>
+ output to stdout. All debug messages are written<br>
+ to ${T}/log.do_taskname, regardless of the debug<br>
+ level.<br>
-n, --dry-run Don't execute, just go through the motions.<br>
-S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_<wbr>HANDLER<br>
Dump out the signature construction information, with<br>
diff --git a/lib/bb/main.py b/lib/bb/main.py<br>
index b3cd2cf..8c948c2 100755<br>
--- a/lib/bb/main.py<br>
+++ b/lib/bb/main.py<br>
@@ -174,10 +174,21 @@ class BitBakeConfigParameters(<wbr>cookerdata.ConfigParameters):<br>
help="Read the specified file after bitbake.conf.")<br>
<br>
parser.add_option("-v", "--verbose", action="store_true", dest="verbose", default=False,<br>
- help="Output more log message data to the terminal.")<br>
+ help="Enable tracing of shell tasks (with 'set -x'). "<br>
+ "Also print bb.note(...) messages to stdout (in "<br>
+ "addition to writing them to ${T}/log.do_<task>).")<br>
<br>
parser.add_option("-D", "--debug", action="count", dest="debug", default=0,<br>
- help="Increase the debug level. You can specify this more than once.")<br>
+ help="Increase the debug level. You can specify this "<br>
+ "more than once. -D sets the debug level to 1, "<br>
+ "where only bb.debug(1, ...) messages are printed "<br>
+ "to stdout; -DD sets the debug level to 2, where "<br>
+ "both bb.debug(1, ...) and bb.debug(2, ...) "<br>
+ "messages are printed; etc. Without -D, no debug "<br>
+ "messages are printed. Note that -D only affects "<br>
+ "output to stdout. All debug messages are written "<br>
+ "to ${T}/log.do_taskname, regardless of the debug "<br>
+ "level.")<br>
<br>
parser.add_option("-q", "--quiet", action="count", dest="quiet", default=0,<br>
help="Output less log message data to the terminal. You can specify this more than once.")<br>
<span class="HOEnZb"><font color="#888888">--<br>
2.7.4<br>
<br>
</font></span></blockquote></div><br></div>