diff options
| author | Chen Qi <Qi.Chen@windriver.com> | 2014-09-04 15:52:44 +0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-09-10 15:38:54 +0100 |
| commit | b5e69717b0a46b088253a2208cb8aed3b82468c0 (patch) | |
| tree | 8c8baa2f3f13428975d544a39ecdb2e9ddb7b40d | |
| parent | f19b1d01e3663301942906861a8ac12269b9e899 (diff) | |
| download | tizen-distro-b5e69717b0a46b088253a2208cb8aed3b82468c0.tar.gz tizen-distro-b5e69717b0a46b088253a2208cb8aed3b82468c0.tar.bz2 tizen-distro-b5e69717b0a46b088253a2208cb8aed3b82468c0.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.
(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>
| -rw-r--r-- | meta/conf/bitbake.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 2771233e3e..468b175edc 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 |