feat(khronos.vulkan-hpp): 1.4.357.1 follows compat.vulkan 1.4.357.3; the macOS note says how to get a device - #398
Merged
Conversation
…the macOS note says how to get a device KHRONOS.VULKAN-HPP 1.4.357.1 -- the same Vulkan-Headers tarball, pinned to compat.vulkan 1.4.357.3, whose Windows artifact carries the loader DLL. A new version rather than a moved pin, because an installed copy records the pin it resolved with. `vulkan-hpp-module` moves to it. This is the half of #395 that could not be verified in #395 itself: the member redirects only the `khronos` namespace to this checkout, so `compat` came from the published index, which did not have 1.4.357.3 until #395 merged. Redirecting `compat` as well is still refused on mcpp 2026.9.11.2 ("≥2 project-level index repos is a known xlings resolution gap"), so the order had to be: merge #395, republish, then this. On #395's own `windows-2022` leg the member failed exactly as predicted (it resolved compat.vulkan 1.4.357.0 and died with 0xC0000135); this change is judged by that leg passing. COMPAT.VULKAN, macOS -- a comment, no behaviour change. The block said only that the ICD is MoltenVK. It now records what was measured on macos-15 (#396): nothing crashes without MoltenVK; a device enumerates when libMoltenVK.dylib and a relative-path manifest sit in <executable dir>/vulkan/icd.d, which the static loader searches first, and that layout survives being moved; or through VK_DRIVER_FILES; and in both cases only with portability enumeration enabled. What mcpp would need to place those files is mcpp-community/mcpp#615. Co-authored-by: sunrisepeak <x.d2learn.org@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
khronos.vulkan-hpp1.4.357.1 — same headers, pin →compat.vulkan1.4.357.3;vulkan-hpp-module→ 1.4.357.1compat.vulkanmacOSruntimecomment — what was measured about getting a device (no behaviour change)Why it is separate from #395
vulkan-hpp-moduleredirects onlykhronosto this checkout, socompatresolves from the published index — which had no 1.4.357.3 until #395 merged. A second project index is still refused on mcpp 2026.9.11.2. So: merge #395 → republish → this.On #395's
windows-2022leg this member failed as predicted (resolved compat.vulkan 1.4.357.0 →0xC0000135). This PR is judged by that leg passing.macOS note, measured on macos-15 (#396)
VK_ERROR_INCOMPATIBLE_DRIVER, 0 devices — no crashlibMoltenVK.dylib+vulkan/icd.d/MoltenVK_icd.json(relativelibrary_path) beside the executableVK_DRIVER_FILESPortability enumeration must be enabled by the program. mcpp deploying those files: mcpp-community/mcpp#615.