[oe-commits] Chen Qi : bitbake.conf: use ??= for IMAGE_ROOTFS_SIZE

[git at git.openembedded.org]

Module: openembedded-core.git
Branch: master-next
Commit: 18f499df6bcbf79d7bd0a99c4c8693268683485f
URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=18f499df6bcbf79d7bd0a99c4c8693268683485f

Author: Chen Qi <Qi.Chen at windriver.com>
Date:   Thu Sep  4 15:52:44 2014 +0800

bitbake.conf: use ??= for IMAGE_ROOTFS_SIZE

Previously, when building core-image-minimal, the rootfs size would
default to 64M because we use '?=' in bitbake.conf and also '?=' in
core-image-minimal.bb.

The thing is, we'd like to have a default value for all images set
in bitbake.conf but still allow each image recipe to set its own default
value which could be overridden by users in local.conf.

Signed-off-by: Chen Qi <Qi.Chen at windriver.com>
Signed-off-by: Ross Burton <ross.burton at intel.com>

---

 meta/conf/bitbake.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 2771233..468b175 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -689,7 +689,7 @@ MACHINE_TASK_PROVIDER ?= "${DEFAULT_TASK_PROVIDER}"
 # The size in Kbytes for the generated image if it is larger than
 # the required size (du -ks IMAGE_ROOTFS * IMAGE_OVERHEAD_FACTOR),
 # and no effect if less than it.
-IMAGE_ROOTFS_SIZE ?= "65536"
+IMAGE_ROOTFS_SIZE ??= "65536"
 
 # Forcefully set CACHE now so future changes to things like 
 # MACHINE don't change the path to the cache