livecd-rootfs/live-build/ubuntu-cpc/hooks/040-vmdk-image.binary

#!/bin/bash -eux
# vi: ts=4 expandtab
#
# Generate VMDK files

case ${SUBPROJECT:-} in
    minimized)
        echo "Skipping minimized $0 build as images won't boot with linux-kvm"
        exit 0
        ;;
    *)
        ;;
esac

extension="disk1.vmdk"

case $ARCH in
         i386|amd64) ;;
                  *) echo "VMDK images are not supported for $ARCH yet.";
                     exit 0;;
esac

. config/functions

if [ -e binary/boot/disk.ext4 ]; then
    create_vmdk binary/boot/disk.ext4 livecd.ubuntu-cpc.disk1.vmdk
fi

if [ -e binary/boot/disk-uefi.ext4 ]; then
    create_vmdk binary/boot/disk-uefi.ext4 livecd.ubuntu-cpc.uefi.vmdk
fi
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00			`#!/bin/bash -eux`
Pre-merge commit 2015-11-13 08:09:26 -07:00			`# vi: ts=4 expandtab`
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00			`#`
			`# Generate VMDK files`

ubuntu-cpc: When performing a minimized build, don't generate artifacts that won't boot with the linux-kvm kernel (LP: #1757223). 2018-03-20 16:10:44 -04:00			`case ${SUBPROJECT:-} in`
			`minimized)`
			`echo "Skipping minimized $0 build as images won't boot with linux-kvm"`
			`exit 0`
			`;;`
			`*)`
			`;;`
			`esac`

ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00			`extension="disk1.vmdk"`
ubuntu-cpc: create VMDK's for disk images if they exist. Remove assumption that disk1.img will exist. 2015-12-07 11:45:58 -07:00
Fix architecture handling in hooks. We know we're always being invoked from a launchpad-buildd-like setup, which passes ARCH and SUBARCH in the environment, because auto/config and auto/build both rely on this. So don't scatter dpkg --print-architecture calls throughout, especially when many of these are not cross-build-aware. 2016-02-05 23:39:56 -08:00			`case $ARCH in`
ubuntu-cpc: create VMDK's for disk images if they exist. Remove assumption that disk1.img will exist. 2015-12-07 11:45:58 -07:00			`i386\|amd64) ;;`
Fix architecture handling in hooks. We know we're always being invoked from a launchpad-buildd-like setup, which passes ARCH and SUBARCH in the environment, because auto/config and auto/build both rely on this. So don't scatter dpkg --print-architecture calls throughout, especially when many of these are not cross-build-aware. 2016-02-05 23:39:56 -08:00			`*) echo "VMDK images are not supported for $ARCH yet.";`
ubuntu-cpc: create VMDK's for disk images if they exist. Remove assumption that disk1.img will exist. 2015-12-07 11:45:58 -07:00			`exit 0;;`
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00			`esac`

Source ubuntu-cpc functions from the right place 2017-05-12 21:20:22 +02:00			`. config/functions`
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00
ubuntu-cpc: create VMDK's for disk images if they exist. Remove assumption that disk1.img will exist. 2015-12-07 11:45:58 -07:00			`if [ -e binary/boot/disk.ext4 ]; then`
			`create_vmdk binary/boot/disk.ext4 livecd.ubuntu-cpc.disk1.vmdk`
			`fi`
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00
			`if [ -e binary/boot/disk-uefi.ext4 ]; then`
ubuntu-cpc: move vmdk creation code into common funtion to support Vagrant Box builds 2015-11-12 17:21:33 -07:00			`create_vmdk binary/boot/disk-uefi.ext4 livecd.ubuntu-cpc.uefi.vmdk`
ubuntu-cpc: generate VMDK disks 2015-11-12 14:48:41 -07:00			`fi`