openembedded-core.git/meta/classes/bootimg.bbclass, branch pyro

bootimg.bbclass: merge it into image-live.bbclass

2016-03-31T12:22:50+00:00

They are doing the same things: create live images, merge them into one
bbclass makes it easy to understand.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

image-live.bbclass: DEPENDS on syslinux

2016-03-31T12:18:12+00:00

The mkisofs requires syslinux/isolinux.bin which is provided by
target syslinux, for pcbios, the depends is already there, but for
EFI, it isn't, so add the depends.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

bootimg.bbclass: only inherit syslinux when pcbios

2016-03-24T21:44:26+00:00

syslinux.bbclass should not be seen when use efi.

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

bootimg.bbclass: fix settings for grub-efi.bbclass

2016-03-24T21:44:26+00:00

Fixed:
- Found potential conflicted var LABELS ...
  Set LABELS to "boot install" would build out broken images when build
  vm + live together, use set_live_vm_vars() to fix the problem.

- Use ROOT and LABEL in boot-directdisk.bbclass and image-foo.bbclass,
  they are not only used by syslinux.bbclass, but also grub-efi.bbclass,
  add "SYSLINUX_" prefix would mislead users.

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

bootimg: set default value for LABELS variable

2016-03-02T23:08:07+00:00

With empty LABELS variable build_efi_cfg skips most of its
functionality producing warning message:
    'LABELS not defined, nothing to do'
This causes build failure for efi images.

Setting default value for LABELS to 'boot install' should fix
this issue.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

syslinux.bbclass: make vm and live can be built together

2016-03-02T23:08:07+00:00

* The vm image(hdddirect, vmdk, qcow2, vdi) and live image (hddimg, iso)
  couldn't be built together because the following vars settings are
  conflicted:
  - SYSLINUX_ROOT (/dev/sda2 vs /dev/ram0)
  - LABELS (boot vs boot install)
  - INITRD (None vs live install)
  - SYSLINUX_CFG (see above)
  Introduce new vars (SYSLINUX_ROOT_VM/_LIVE, the samilar to others) to
  make them can work together, now we can build all of them together:

  IMAGE_FSTYPES += "live iso hddimg hdddirect vmdk qcow2 vdi"

* Use SYSLINUX_CFG rather than SYSLINUXCFG to keep align with others
  SYSLINUX vars.

* The SYSLINUX_TIMEOUT had been set, but it didn't work since
  AUTO_SYSLINUXMENU wasn't set, this would cause confusions, so also set
  AUTO_SYSLINUXMENU.

* Move SYSLINUX_PROMPT and SYSLINUX_TIMEOUT to syslinux.bbclass rather
  than in separate classes since they are the same.

* Set SYSLINUX_TIMEOUT to 50 to have a unique timeout for syslinux.

[YOCTO #9161]

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

bootimg/image-vm/image-live: Improve image dependencies

2016-01-19T16:35:37+00:00

Now that image generation consists of separate tasks, we can improve
the dependencies in these classes. We can also incorporate the tasks
within do_image_complete instead of do_build so we have a specific task
for when the deploy directory is populated with images.

This fixes various expectations about do_image_completed and the way
I'd tried to use it to fix some sanity test problems.

Signed-off-by: Richard Purdie

bootimg/image: Enhance bootimg to respect RM_OLD_IMAGE

2016-01-19T16:35:37+00:00

Currently, iso and hddimg links don't respect RM_OLD_IMAGE. This
updates them to use the common symlinks code so that they behave
like the rest of the system.

Signed-off-by: Richard Purdie

IMAGES_FSTYPES: default to EXT4

2015-08-16T08:25:17+00:00

The following IMAGES_FSTYPES defaulted to ext3:
"vmdk", "vdi", "qcow2", "live", "iso", "hddimg"

This patch changes the default for those IMAGES_FSTYPES to
ext4 in order to bring the images more in line with other BSPs.

Besides improvements in performance and reliability ext4 provides
additional functionality as well (option to turn off the journaling,
dynamic resizing of VDI volumes etc.).

Signed-off-by: Juro Bystricky 
Signed-off-by: Richard Purdie

bootimg.bbclass:iso: determine the -iso-level only if there is a rootfs

2015-08-09T22:14:31+00:00

It may be possible that some bootable images do not use a rootfs; this
may be the case if the bootable image utilize only an initrd for all its
needs.

If there is not rootfs, the size calculation will fail. Furthermore, given
that the iso9660 conformance level is determined using the size of rootfs,
it makes sense to not make the calculation if there is not such rootfs.

Signed-off-by: Ricardo Neri 
Signed-off-by: Richard Purdie