board/shredos/make_iso_file.sh

#!/bin/bash -e

if grep -Eq "^BR2_ARCH_IS_64=y$" "${BR2_CONFIG}"; then
    MKIMAGE_ARCH=x86-64
else
    MKIMAGE_ARCH=i686
fi

version=$(cat board/shredos/fsoverlay/etc/shredos/version.txt)

SUFFIXISO="${version}_$(date +%Y%m%d)"
FINAL_ISO_PATH="${BINARIES_DIR}/shredos-${SUFFIXISO}.iso"

mv "${BINARIES_DIR}/rootfs.iso9660" "${FINAL_ISO_PATH}"             || exit 1

GREEN="\033[0;32m"
RESET="\033[0m"

printf "%b" "$GREEN"
echo
echo "==============================================="
echo "  ISO image '${FINAL_ISO_PATH}'"
echo "  (for '${MKIMAGE_ARCH}' architecture)"
echo "  CREATED SUCCESSFULLY!"
echo "==============================================="
echo
printf "%b" "$RESET"

exit 0
fix(shredos): refactor post-process scripts Post-processing used a static (outdated?) GRUB image for USB image generation, but it is better to use the GRUB image produced as part of the building process, which ensures that the actual compiled GRUB version is used as bootloader in our images and not an outdated one. Post-processing previously embedded the 64-bit EFI bootloader to 32-bit builds, as no architecture checks were in place. This was changed to check for architecture and embed the correct EFI bootloader for the respective target architecture instead. The GRUB configuration was changed to use a menu, to allow the user to choose between standard and nomodeset parameters, while also allowing the user to edit the command line to append other kernel parameters they may need for their systems. The vanity kernel image name was returned to bzImage to clearly mark the image for what it is, and to remain consistent with the ISO file generation where we have no direct control over the image now. Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com> 2025-11-18 07:32:51 +01:00			`#!/bin/bash -e`

			`if grep -Eq "^BR2_ARCH_IS_64=y$" "${BR2_CONFIG}"; then`
chore(board): copy over 32-bit EFI for IMG 2026-02-18 10:58:13 +01:00			`MKIMAGE_ARCH=x86-64`
fix(shredos): refactor post-process scripts Post-processing used a static (outdated?) GRUB image for USB image generation, but it is better to use the GRUB image produced as part of the building process, which ensures that the actual compiled GRUB version is used as bootloader in our images and not an outdated one. Post-processing previously embedded the 64-bit EFI bootloader to 32-bit builds, as no architecture checks were in place. This was changed to check for architecture and embed the correct EFI bootloader for the respective target architecture instead. The GRUB configuration was changed to use a menu, to allow the user to choose between standard and nomodeset parameters, while also allowing the user to edit the command line to append other kernel parameters they may need for their systems. The vanity kernel image name was returned to bzImage to clearly mark the image for what it is, and to remain consistent with the ISO file generation where we have no direct control over the image now. Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com> 2025-11-18 07:32:51 +01:00			`else`
chore(board): rename iso arch to i686 2026-02-17 17:23:52 +01:00			`MKIMAGE_ARCH=i686`
fix(shredos): refactor post-process scripts Post-processing used a static (outdated?) GRUB image for USB image generation, but it is better to use the GRUB image produced as part of the building process, which ensures that the actual compiled GRUB version is used as bootloader in our images and not an outdated one. Post-processing previously embedded the 64-bit EFI bootloader to 32-bit builds, as no architecture checks were in place. This was changed to check for architecture and embed the correct EFI bootloader for the respective target architecture instead. The GRUB configuration was changed to use a menu, to allow the user to choose between standard and nomodeset parameters, while also allowing the user to edit the command line to append other kernel parameters they may need for their systems. The vanity kernel image name was returned to bzImage to clearly mark the image for what it is, and to remain consistent with the ISO file generation where we have no direct control over the image now. Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com> 2025-11-18 07:32:51 +01:00			`fi`

			`version=$(cat board/shredos/fsoverlay/etc/shredos/version.txt)`

			`SUFFIXISO="${version}_$(date +%Y%m%d)"`
			`FINAL_ISO_PATH="${BINARIES_DIR}/shredos-${SUFFIXISO}.iso"`

			`mv "${BINARIES_DIR}/rootfs.iso9660" "${FINAL_ISO_PATH}" \|\| exit 1`

			`GREEN="\033[0;32m"`
			`RESET="\033[0m"`

			`printf "%b" "$GREEN"`
			`echo`
			`echo "==============================================="`
			`echo " ISO image '${FINAL_ISO_PATH}'"`
			`echo " (for '${MKIMAGE_ARCH}' architecture)"`
			`echo " CREATED SUCCESSFULLY!"`
			`echo "==============================================="`
			`echo`
			`printf "%b" "$RESET"`

			`exit 0`