local.conf.sample: Use ?= when setting SDKMACHINE

This is a more sensible default which is also needed when using our
autobuilder configuration, which changes SDKMACHINE between builds by
setting an environment variable.

Also made spacing around = more consistent for a couple of other
variables.

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>

diff --git a/build/conf/local.conf.sample b/build/conf/local.conf.sample
index 78c3bd144ea6b96b58b6e848bfb6486c12714611..37c34d8f5e96aeddf071972725ea1bbb6d37b7b1 100644 (file)
--- a/build/conf/local.conf.sample
+++ b/build/conf/local.conf.sample
@@ -132,7 +132,7 @@ ENABLE_BINARY_LOCALE_GENERATION = "1"
 # packages for architectures other than the host i.e. building i586 packages
 # on an x86_64 host.
 # Supported values are i586 and x86_64
-#SDKMACHINE="i586"
+#SDKMACHINE ?= "i586"
 
 # Poky can try and fetch packaged-staging packages from a http, https or ftp
 # mirror. Set this variable to the root of a pstage directory on a server.
@@ -140,8 +140,8 @@ ENABLE_BINARY_LOCALE_GENERATION = "1"
 
 # Set IMAGETEST to qemu if you want to build testcases and start 
 # testing in qemu after do_rootfs.
-#IMAGETEST="qemu"
+#IMAGETEST = "qemu"
 
 # By default testing will run the sanitytest suite. If you want to run other tests
 # (e.g. bat), list them here
-#TEST_SCEN="sanitytest bat"
+#TEST_SCEN = "sanitytest bat"