bitbake.conf: use ??= for IMAGE_ROOTFS_SIZE
cover bitbake.conf: use ??= for IMAGE_ROOTFS_SIZE
The following changes since commit 4c0a9ccbad2889b27b4b1d2ab91215a4bdcca3ce:
python-numpy: Fix build for mips64 (2014-09-01 18:00:32 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/IMAGE_ROOTFS_SIZE
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/IMAGE_ROOTFS_SIZE
Chen Qi (1):
bitbake.conf: use ??= for IMAGE_ROOTFS_SIZE
meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 1 line
1.9.1
PATCH 1/1 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.
--- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/bitbake.conf +1 -1
@@ -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
Signature · 1 line
1.9.1