Skip to content

BUILDING: copy the runtime's build manifest into the payload - #260

Merged
phantoslayer21 merged 1 commit into
mainfrom
docs/building-runtime-manifest
Nov 16, 2026
Merged

phantoslayer21 merged 1 commit into
mainfrom
docs/building-runtime-manifest

Conversation

@phantoslayer21

Copy link
Copy Markdown
Owner

The payload packager (clean/installer/tools/make_payload.py) accepts a runtime library only when its build manifest, wronggpu_runtime.build.json (written by clean/runner/build.py next to the library), sits next to it and matches its SHA-256. BUILDING.md's payload step copied only wronggpu_runtime.dll, so a build that follows it is refused at packaging.

  • The payload table and the copy commands now include wronggpu_runtime.build.json.
  • One paragraph says why: keep the two together and do not change the library after the build (no signing or stripping). The manifest is read for that check and is not shipped (make_payload.py skips it).

Docs only.

clean/runner/build.py writes wronggpu_runtime.build.json next to the runtime
library, and the payload packager refuses a runtime library without it (or one
whose SHA-256 does not match it). The payload step now copies the manifest with
the library and says why; the manifest is read for that check and not shipped.

Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
@phantoslayer21
phantoslayer21 merged commit c554d18 into main Nov 16, 2026
10 checks passed
@phantoslayer21
phantoslayer21 deleted the docs/building-runtime-manifest branch November 16, 2026 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant