yoebuild/yoe v0.10.15

on GitHub

• TUI Setup gained a QEMU settings sub-screen. Press s then Enter on "QEMU
  settings" to adjust the guest's RAM with ←/→, toggle the graphical display,
  and add or remove host:guest port forwards for yoe run. Choices persist to
  local.star and apply automatically the next time you launch the guest — no
  need to remember --memory, --display, or --port flags for routine work.
• The QEMU settings screen shows the equivalent qemu command. A live preview
  at the bottom of the sub-screen renders the exact qemu-system-* invocation
  yoe run would emit with the current Memory / Display / Ports values, so you
  can confirm what each tweak changes before launching — and copy-paste the line
  to drive QEMU directly.
• New qt-image boots straight into a Qt 6 Quick demo on the framebuffer.
  Build with yoe build qt-image and run with yoe run qt-image --display;
  QEMU opens a window showing the demo scene (a "Hello from yoe!" message
  rendered through the linuxfb platform plugin and the software scene graph).
  Useful as a quick end-to-end check that a yoe-built image's graphical stack
  works on hardware that ships virtio-gpu, Bochs, or a plain VESA/EFI
  framebuffer.
• yoe run --display now actually opens a QEMU window. Previously the flag
  dropped -nographic but didn't tell QEMU what to display with; running an
  image showed only an empty terminal. The launcher now attaches a virtio-vga
  adapter and keeps the serial console muxed onto host stdio
  (-serial mon:stdio) so kernel logs stay visible alongside the framebuffer
  window. Headless yoe run (no --display) is unchanged.
• The kernel ships framebuffer and DRM drivers for QEMU and common PC GPUs out
  of the box. linux now merges a graphics.cfg fragment that enables
  virtio-gpu, Bochs, vesafb, efifb, and DRM fbdev emulation, so every yoe image
  exposes /dev/fb0 on first boot without per-image configuration.

To update, run: yoe update
Or download the binary for your architecture and place it in your PATH.
Note: Yoe is in heavy development. We recommend cleaning your build directory and re-creating projects (yoe init) with each new release.