Repository navigation
Add llama.cpp b10069 under the unified mwrap identity - #5
Merged
Merged
Conversation
Sunrisepeak
marked this pull request as ready for review
October 24, 2026 22:59
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.
Preserve the pinned unmodified llama.cpp tree and C API. Move the public module and typed macro constants into mcpplibs.mwrap.llamacpp, retain CPU/Metal/Vulkan feature ownership, and provide an actual CPU project template. The upstream build-number version is exact; independent mwrap-b10069 tags cannot overwrite the legacy b10069 release.
English README.md and Chinese README.zh.md follow the reviewed common layout, including full module import bullets before quickstart and a uniform Upstream link. Existing legacy package identities and release resources stay intact; the flat mwrap descriptor is prepared in index PR #564.
Validation at
0d55de134c5c16bc31b5fb1e91c5946236b8b829: All eight exact-head native/source/release-contract checks pass, including CPU, ARM64, Metal and Vulkan jobs. The complete 117-test Python suite, LLVM23 and GCC16 macro consumers pass locally. Export generation, upstream snapshot and source-lock checks retain immutable upstream bytes. GPU claims remain bounded by the documented driver/runtime configurations.Self-review checked package/module identity, first-version mapping, generated exports and macro ownership, source/runtime dependencies, template rendering, bilingual links, archive byte equality and platform limits. Exact squash-commit CI is required before tagging; final GitCode mirrors and public-index installation/relocation remain publication gates. No mcpp engine changes.