Repository navigation
Normalize build paths in distributable QEMU artifacts - #164
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.
Normalize private build paths in distributable QEMU outputs at the producer. C/C++ source-location macros map to stable public roots; GLib uses a logical
/usrprefix with staged installation and host-only pkg-config relocation. Existing assertion settings, QEMU/controller source, firmware profiles and clocks remain unchanged. Old dependency caches are rejected, and executable/source-package/manifest checks fail closed on actual private prefixes.Validation: all eight target libraries and QEMU were rebuilt; the new WASM has zero actual producer/home prefixes across all 14 sections. The corresponding source and 2,127 exported assets passed independent checks. Seventeen builder tests, ten exporter tests, real C/C++ positive/negative controls and the real WASM32/libffi ABI controls pass. Cardputer-ADV executes the new runtime through the actual firmware/controller/frame path with 69/69 checks and six Worker targets closed; the complete 20-case gate is still running. This does not resolve the separate engine-target closure failure in regular hosted Pages CI.
See the fixed executable-validation record for the source/firmware/runtime hashes, path scan, guest inputs/frame state, cleanup, reproducible patch and limits. No firmware or ROM is bundled.