From 4dc1a2506ea78dc0eb50b7f720296ddcb080408a Mon Sep 17 00:00:00 2001 From: Bill Traynor Date: Thu, 25 Apr 2013 12:54:10 -0400 Subject: user-manual-metadata: Formatting the copied content from YP. Formatted the 'Running a Task' section that was copied from the YP Reference Manual for 80 column anherence. Signed-off-by: Bill Traynor --- doc/user-manual/user-manual-metadata.xml | 78 +++++++++++++++++--------------- 1 file changed, 42 insertions(+), 36 deletions(-) diff --git a/doc/user-manual/user-manual-metadata.xml b/doc/user-manual/user-manual-metadata.xml index 2f221550d..444d14c52 100644 --- a/doc/user-manual/user-manual-metadata.xml +++ b/doc/user-manual/user-manual-metadata.xml @@ -572,19 +572,21 @@ need to import them. Tasks can either be a shell task or a Python task. For shell tasks, BitBake writes a shell script to - ${WORKDIR}/temp/run.do_taskname.pid and then executes the script. - The generated shell script contains all the exported variables, and the shell functions - with all variables expanded. - Output from the shell script goes to the file ${WORKDIR}/temp/log.do_taskname.pid. - Looking at the expanded shell functions in the run file and the output in the log files - is a useful debugging technique. + ${WORKDIR}/temp/run.do_taskname.pid and then + executes the script. + The generated shell script contains all the exported variables, and + the shell functions with all variables expanded. + Output from the shell script goes to the file + ${WORKDIR}/temp/log.do_taskname.pid. + Looking at the expanded shell functions in the run file and the + output in the log files is a useful debugging technique. - For Python tasks, BitBake executes the task internally and logs information to the - controlling terminal. - Future versions of BitBake will write the functions to files similar to the way - shell tasks are handled. + For Python tasks, BitBake executes the task internally and logs + information to the controlling terminal. + Future versions of BitBake will write the functions to files + similar to the way shell tasks are handled. Logging will be handled in a way similar to shell tasks as well. @@ -593,31 +595,34 @@ need to import them. - When running a task, BitBake tightly controls the execution environment - of the build tasks to make sure unwanted contamination from the build machine - cannot influence the build. + When running a task, BitBake tightly controls the execution + environment of the build tasks to make sure unwanted contamination + from the build machine cannot influence the build. Consequently, if you do want something to get passed into the build task's environment, you must take a few steps: - Tell BitBake to load what you want from the environment - into the data store. - You can do so through the BB_ENV_EXTRAWHITE - variable. - For example, assume you want to prevent the build system from - accessing your $HOME/.ccache directory. + Tell BitBake to load what you want from the + environment into the data store. + You can do so through the + BB_ENV_EXTRAWHITE variable. + For example, assume you want to prevent the build system + from accessing your $HOME/.ccache + directory. The following command tells BitBake to load - CCACHE_DIR from the environment into the data - store: + CCACHE_DIR from the environment into + the data store: export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE CCACHE_DIR" - Tell BitBake to export what you have loaded into the - environment store to the task environment of every running task. - Loading something from the environment into the data store - (previous step) only makes it available in the datastore. - To export it to the task environment of every running task, - use a command similar to the following in your - local.conf or distro configuration file: + Tell BitBake to export what you have loaded into + the environment store to the task environment of every running + task. + Loading something from the environment into the data store + ()previous step) only makes it available in the datastore. + To export it to the task environment of every running task, + use a command similar to the following in your + local.conf or distro configuration + file: export CCACHE_DIR @@ -625,14 +630,15 @@ need to import them. - A side effect of the previous steps is that BitBake records the variable - as a dependency of the build process in things like the shared state - checksums. - If doing so results in unnecessary rebuilds of tasks, you can whitelist the - variable so that the shared state code ignores the dependency when it creates - checksums. - For information on this process, see the BB_HASHBASE_WHITELIST - example in the "Checksums (Signatures)" section. + A side effect of the previous steps is that BitBake records the + variable as a dependency of the build process in things like the + shared state checksums. + If doing so results in unnecessary rebuilds of tasks, you can + whitelist the variable so that the shared state code ignores the + dependency when it creates checksums. + For information on this process, see the + BB_HASHBASE_WHITELIST example in the + "Checksums (Signatures)" section.
-- cgit 1.2.3-korg