Yocto 2.3
Move OpenBMC to Yocto 2.3(pyro).
Tested: Built and verified Witherspoon and Palmetto images
Change-Id: I50744030e771f4850afc2a93a10d3507e76d36bc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Resolves: openbmc/openbmc#2461
diff --git a/import-layers/yocto-poky/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/import-layers/yocto-poky/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
index 4d58dc4..ca7f724 100644
--- a/import-layers/yocto-poky/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/import-layers/yocto-poky/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -504,9 +504,19 @@
Read the specified file before bitbake.conf.
-R POSTFILE, --postread=POSTFILE
Read the specified file after bitbake.conf.
- -v, --verbose Output more log message data to the terminal.
- -D, --debug Increase the debug level. You can specify this more
- than once.
+ -v, --verbose Enable tracing of shell tasks (with 'set -x').
+ Also print bb.note(...) messages to stdout (in
+ addition to writing them to ${T}/log.do_<task>).
+ -D, --debug Increase the debug level. You can specify this
+ more than once. -D sets the debug level to 1,
+ where only bb.debug(1, ...) messages are printed
+ to stdout; -DD sets the debug level to 2, where
+ both bb.debug(1, ...) and bb.debug(2, ...)
+ messages are printed; etc. Without -D, no debug
+ messages are printed. Note that -D only affects
+ output to stdout. All debug messages are written
+ to ${T}/log.do_taskname, regardless of the debug
+ level.
-n, --dry-run Don't execute, just go through the motions.
-S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER
Dump out the signature construction information, with
@@ -529,8 +539,8 @@
-l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS
Show debug logging for the specified logging domains
-P, --profile Profile the command and save reports.
- -u UI, --ui=UI The user interface to use (depexp, goggle, hob, knotty
- or ncurses - default knotty).
+ -u UI, --ui=UI The user interface to use (taskexp, knotty or
+ ncurses - default knotty).
-t SERVERTYPE, --servertype=SERVERTYPE
Choose which server type to use (process or xmlrpc -
default process).
@@ -543,6 +553,7 @@
-B BIND, --bind=BIND The name/address for the bitbake server to bind to.
--no-setscene Do not run any setscene tasks. sstate will be ignored
and everything needed, built.
+ --setscene-only Only run setscene tasks, don't run any real tasks.
--remote-server=REMOTE_SERVER
Connect to the specified server.
-m, --kill-server Terminate the remote server.
@@ -665,21 +676,21 @@
</para>
<para>
- When you generate a dependency graph, BitBake writes four files
+ When you generate a dependency graph, BitBake writes three files
to the current working directory:
<itemizedlist>
- <listitem><para><emphasis><filename>package-depends.dot</filename>:</emphasis>
- Shows BitBake's knowledge of dependencies between
- runtime targets.
+ <listitem><para>
+ <emphasis><filename>recipe-depends.dot</filename>:</emphasis>
+ Shows dependencies between recipes (i.e. a collapsed version of
+ <filename>task-depends.dot</filename>).
</para></listitem>
- <listitem><para><emphasis><filename>pn-depends.dot</filename>:</emphasis>
- Shows dependencies between build-time targets
- (i.e. recipes).
- </para></listitem>
- <listitem><para><emphasis><filename>task-depends.dot</filename>:</emphasis>
+ <listitem><para>
+ <emphasis><filename>task-depends.dot</filename>:</emphasis>
Shows dependencies between tasks.
+ These dependencies match BitBake's internal task execution list.
</para></listitem>
- <listitem><para><emphasis><filename>pn-buildlist</filename>:</emphasis>
+ <listitem><para>
+ <emphasis><filename>pn-buildlist</filename>:</emphasis>
Shows a simple list of targets that are to be built.
</para></listitem>
</itemizedlist>