summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-12-01 11:58:41 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-01-30 16:16:13 +0000
commit0e676f74c555a7a7deebd3d1e9e8c996bd6ab9a2 (patch)
tree7ec6c88152fff070cd478de7003ea16e7c7adfd4 /documentation
parent26666187e3e8b129485c442dc72c7e51c91c5e8d (diff)
downloadpoky-0e676f74c555a7a7deebd3d1e9e8c996bd6ab9a2.tar.gz
build.py: Be determistic about a function's cwd
There is a subtle but nasty problem that a function's cwd can vary depending on whether ${B} (often ${S}) exists before the funciton is called or not. Most functions in the system can cope with this but its bad practise and I've just witnessed build failures resulting from this during image generation from bootimg.bbclass. I also suspect this could explain some odd fetcher behaviour witnessed in the past. This change ensures we always call funcitons with a specific build directory making things deterministic. (Bitbake rev: ef0888f83fa4408eb768257d7e03700202faad18) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
0 files changed, 0 insertions, 0 deletions