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. (From OE-Core rev: 18f499df6bcbf79d7bd0a99c4c8693268683485f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
3a7769329e
commit
5e18549574
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue