summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/technical-details.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-12-14 15:36:47 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-30 16:05:50 +0000
commit85408dfd36f339b0954b1573efdfd8eb00935e9d (patch)
tree8f749718fd3273457cb4d7b1fe84f1d584092ddf /documentation/poky-ref-manual/technical-details.xml
parent43fb63af31d3d444229af93b16c6437739d9012a (diff)
downloadpoky-85408dfd36f339b0954b1573efdfd8eb00935e9d.tar.gz
documentation/poky-ref-manual/ref-bitbake.xml: Updated BitBake Running a Task
I added more information about how BitBake actually runs a task. The information has to do with how tightly BB controls the execution environment of the build tasks to prevent contamination from the build machine from leaking into the task execution environment. This tight control actually causes some unexpected behavior during builds. For example, when a user exports and BB_ENV_EXTRAWHITE an environment item such as CCACHE_DIR, the effects of the environment item never make it to the BB task execution environment. They only make it to the data store. The user actually has to take some extra steps to export that environment item into the task execution environment. The added information I put into the "Running a Task" section describes these extra steps. Fixes [YOCTO #689] Reported-by: Wolfgang Denk <wd@denx.de> (From yocto-docs rev: f75a9d384c0d5ccaefe7ac2195917531b153cf5e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/technical-details.xml')
0 files changed, 0 insertions, 0 deletions