aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChen Qi <Qi.Chen@windriver.com>2014-09-04 15:52:44 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-09-10 15:19:57 +0100
commit18f499df6bcbf79d7bd0a99c4c8693268683485f (patch)
treecd0ac9cc9adbb451e49629bb49f30541f95ceb1b
parent4a4877c2e7cdcb8a1d0a54add600c0cd4e92e647 (diff)
downloadopenembedded-core-contrib-18f499df6bcbf79d7bd0a99c4c8693268683485f.tar.gz
openembedded-core-contrib-18f499df6bcbf79d7bd0a99c4c8693268683485f.tar.bz2
openembedded-core-contrib-18f499df6bcbf79d7bd0a99c4c8693268683485f.zip
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@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
-rw-r--r--meta/conf/bitbake.conf2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 2771233e3ea..468b175edc6 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