diff options
| author | Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> | 2011-12-13 20:19:47 +0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-12-16 16:16:06 +0000 |
| commit | 17f7f3a43e863d9e2a16dd02face5137a4f4b225 (patch) | |
| tree | 6ec89966cff25d4d64ab953eabe9360f475f6159 /meta/recipes-sato | |
| parent | bf10cc692491acd615b503779c44e6d7ab3ffe68 (diff) | |
| download | openembedded-core-17f7f3a43e863d9e2a16dd02face5137a4f4b225.tar.gz openembedded-core-17f7f3a43e863d9e2a16dd02face5137a4f4b225.tar.bz2 openembedded-core-17f7f3a43e863d9e2a16dd02face5137a4f4b225.tar.xz openembedded-core-17f7f3a43e863d9e2a16dd02face5137a4f4b225.zip | |
bitbake.conf, core-image-minimal-initramfs: add INITRAMFS_FSTYPES
Initramfs images don't benefit from usual IMAGE_FSTYPES overrides. The
only sane values for them are "cpio.XXX". If IMAGE_FSTYPES is set to
include 'live', building core-image-minimal-initramfs can result in
build error, if the image is built before the kernel. To stop initramfs
images from responding on IMAGE_FSTYPES settings, but still allow
users/developers to override defaults (e.g. to generate "cpio.lzma"
initramfs), introduce INITRAMFS_FSTYPES variable, by default set to
"cpio.gz".
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-sato')
0 files changed, 0 insertions, 0 deletions