diff options
Diffstat (limited to 'documentation/dev-manual/debugging.rst')
-rw-r--r-- | documentation/dev-manual/debugging.rst | 29 |
1 files changed, 14 insertions, 15 deletions
diff --git a/documentation/dev-manual/debugging.rst b/documentation/dev-manual/debugging.rst index 9fb159eae6..3c5609cef5 100644 --- a/documentation/dev-manual/debugging.rst +++ b/documentation/dev-manual/debugging.rst | |||
@@ -108,7 +108,7 @@ Viewing Variable Values | |||
108 | Sometimes you need to know the value of a variable as a result of | 108 | Sometimes you need to know the value of a variable as a result of |
109 | BitBake's parsing step. This could be because some unexpected behavior | 109 | BitBake's parsing step. This could be because some unexpected behavior |
110 | occurred in your project. Perhaps an attempt to :ref:`modify a variable | 110 | occurred in your project. Perhaps an attempt to :ref:`modify a variable |
111 | <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:modifying existing | 111 | <bitbake-user-manual/bitbake-user-manual-metadata:modifying existing |
112 | variables>` did not work out as expected. | 112 | variables>` did not work out as expected. |
113 | 113 | ||
114 | BitBake's ``-e`` option is used to display variable values after | 114 | BitBake's ``-e`` option is used to display variable values after |
@@ -282,15 +282,14 @@ Viewing Task Variable Dependencies | |||
282 | ================================== | 282 | ================================== |
283 | 283 | ||
284 | As mentioned in the | 284 | As mentioned in the |
285 | ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-execution:checksums (signatures)`" section of the BitBake | 285 | ":ref:`bitbake-user-manual/bitbake-user-manual-execution:checksums (signatures)`" |
286 | User Manual, BitBake tries to automatically determine what variables a | 286 | section of the BitBake User Manual, BitBake tries to automatically determine |
287 | task depends on so that it can rerun the task if any values of the | 287 | what variables a task depends on so that it can rerun the task if any values of |
288 | variables change. This determination is usually reliable. However, if | 288 | the variables change. This determination is usually reliable. However, if you |
289 | you do things like construct variable names at runtime, then you might | 289 | do things like construct variable names at runtime, then you might have to |
290 | have to manually declare dependencies on those variables using | 290 | manually declare dependencies on those variables using ``vardeps`` as described |
291 | ``vardeps`` as described in the | 291 | in the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`" |
292 | ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:variable flags`" section of the BitBake | 292 | section of the BitBake User Manual. |
293 | User Manual. | ||
294 | 293 | ||
295 | If you are unsure whether a variable dependency is being picked up | 294 | If you are unsure whether a variable dependency is being picked up |
296 | automatically for a given task, you can list the variable dependencies | 295 | automatically for a given task, you can list the variable dependencies |
@@ -457,7 +456,7 @@ out), then you can use the ``-f`` option. | |||
457 | 456 | ||
458 | The reason ``-f`` is never required when running the | 457 | The reason ``-f`` is never required when running the |
459 | :ref:`ref-tasks-devshell` task is because the | 458 | :ref:`ref-tasks-devshell` task is because the |
460 | [\ :ref:`nostamp <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:variable flags>`\ ] | 459 | [\ :ref:`nostamp <bitbake-user-manual/bitbake-user-manual-metadata:variable flags>`\ ] |
461 | variable flag is already set for the task. | 460 | variable flag is already set for the task. |
462 | 461 | ||
463 | The following example shows one way you can use the ``-f`` option:: | 462 | The following example shows one way you can use the ``-f`` option:: |
@@ -572,10 +571,10 @@ log to ``${T}/log.do_``\ `task`, and can also log to standard output | |||
572 | - ``bb.note(msg)``: Writes "NOTE: msg" to the log. Also logs to | 571 | - ``bb.note(msg)``: Writes "NOTE: msg" to the log. Also logs to |
573 | stdout if BitBake is called with "-v". | 572 | stdout if BitBake is called with "-v". |
574 | 573 | ||
575 | - ``bb.debug(level, msg)``: Writes "DEBUG: msg" to the | 574 | - ``bb.debug(level, msg)``: Writes "DEBUG: msg" to the log. Also logs to |
576 | log. Also logs to stdout if the log level is greater than or equal to | 575 | stdout if the log level is greater than or equal to level. See the |
577 | level. See the ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-intro:usage and syntax`" option | 576 | ":ref:`bitbake-user-manual/bitbake-user-manual-intro:usage and syntax`" |
578 | in the BitBake User Manual for more information. | 577 | option in the BitBake User Manual for more information. |
579 | 578 | ||
580 | - ``bb.warn(msg)``: Writes "WARNING: msg" to the log while also | 579 | - ``bb.warn(msg)``: Writes "WARNING: msg" to the log while also |
581 | logging to stdout. | 580 | logging to stdout. |