[meta-freescale] [Documentation][PATCH 1/2] scripts: bitbake-metadata2doc.sh: use a fresh build directory

[Mario Domenech Goulart]

Before this change we were using a hardcoded build directory
("build").  That approach could lead to problems if the build
directory already existed and contained settings other than the
default ones (setup-environment would not overwrite conf/local.conf
and/or bblayers.conf).

This patch changes that by creating a fresh build directory, thus
making setup-environment create new configuration files with the
default settings, which will make scripts generate more deterministic
results.

Signed-off-by: Mario Domenech Goulart <mario at ossystems.com.br>
---
 scripts/bitbake-metadata2doc.sh |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/scripts/bitbake-metadata2doc.sh b/scripts/bitbake-metadata2doc.sh
index d0cfed8..64e6bc0 100755
--- a/scripts/bitbake-metadata2doc.sh
+++ b/scripts/bitbake-metadata2doc.sh
@@ -75,9 +75,12 @@ marshalled_data_file=doc-data.pckl
 
 rm -f $anchor/$marshalled_data_file
 
+build_dir=`mktemp -d --tmpdir=$yocto_dir`
+
 for machine in $machines; do
     cd $yocto_dir
-    MACHINE=$machine . ./setup-environment build
+    echo "Using $build_dir as build directory"
+    MACHINE=$machine . ./setup-environment `basename $build_dir`
 
     MACHINE=$machine python $anchor/extract-bitbake-metadata.py \
         $anchor/$marshalled_data_file \
@@ -124,5 +127,7 @@ for machine in $machines; do
     fi
 done
 
+rm -rf $build_dir
+
 cd $anchor
 python ./bitbake-metadata2doc.py $marshalled_data_file "../release-notes/source" "$yocto_dir" "$gitdm_dir" "$start_commit" "$end_commit"
-- 
1.7.10.4