Fix loader include under V3 - #33
Merged
Merged
Conversation
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
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.
Summary
@VMODROOTso generated C does not depend on the compiler's working directory-new-compilermastercompatibility lane as an advisory drift checkWhy
v_vulkan_videoexposed this under V3: generatedsrc.cincludedloader_bridge.hwithout an include path and GCC could not find it. The released compiler happened to preserve the module-relative lookup. Using V's documented module-root path makes the binding portable across both frontends.Local verification
git diff --checkThe PR matrix provides the authoritative pinned V3 regression check.