From 79c58f422fa9012519e85ab77de0478cf511c82b Mon Sep 17 00:00:00 2001 From: speak-agent <248744407+speak-agent@users.noreply.github.com> Date: Sat, 5 Sep 2026 21:20:02 +0800 Subject: [PATCH] fix(examples): 10 declares the lavapipe payload it runs on without a GPU The README states the artifact runs on the software driver payload when no vendor ICD is present, but the manifest never named it, so a machine with no GPU had no device at all. The example now provisions xim:mesa-lavapipe like its other payloads. --- examples/10-vulkan-compute/app/mcpp.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/examples/10-vulkan-compute/app/mcpp.toml b/examples/10-vulkan-compute/app/mcpp.toml index 2dd09a9a..e67ec3da 100644 --- a/examples/10-vulkan-compute/app/mcpp.toml +++ b/examples/10-vulkan-compute/app/mcpp.toml @@ -29,6 +29,12 @@ vulkan-runtime = "2026.09.05" # which is what every CI runner in this ecosystem is. [xlings.workspace] "xim:glslang" = "15.1.0" +# A Vulkan device that needs no GPU: Mesa's lavapipe as a payload, complete +# with its own LLVM. On a machine with a vendor ICD the loader lists both and +# the program picks the discrete GPU; with none -- a CI runner, a sandbox -- +# this is the device the artifact runs on. Selected explicitly with +# VK_DRIVER_FILES=/share/vulkan/icd.d/lvp_icd.x86_64.json. +"xim:mesa-lavapipe" = "26.2.1" [build] # What this build compiles device code FOR. `vulkan1.2` is the SPIR-V target