Repository navigation
Conversation
README advertises Metal, but the build script list has no Apple entry and none of the recipes pass QWEN_SHARED, so a macOS user following the docs ends up with libqwen-core.a only, and a ctypes / bindgen / cgo consumer has no dylib to load. ./buildmetal.sh follows the sibling scripts step for step and pins the platform defaults (GGML_METAL, GGML_METAL_EMBED_LIBRARY, GGML_BLAS) plus QWEN_SHARED=ON, so the tree also gets libqwen.dylib. Verified from a clean checkout on an M4: the shared target exports the 18 qt_* symbols with no pipeline_* or backend_* symbol visible, the CLI tools still link the static core library, and a ctypes caller loads the dylib and synthesises through the Metal backend (device detected, output audio transcribes back to the input text).
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.
README advertises Metal, but the build script list has no Apple entry and none of the recipes pass QWEN_SHARED, so a macOS user following the docs ends up with libqwen-core.a only, and a ctypes / bindgen / cgo consumer has no dylib to load.
./buildmetal.sh follows the sibling scripts step for step and pins the platform defaults (GGML_METAL, GGML_METAL_EMBED_LIBRARY, GGML_BLAS) plus QWEN_SHARED=ON, so the tree also gets libqwen.dylib. Verified from a clean checkout on an M4: the shared target exports the 18 qt_* symbols with no pipeline_* or backend_* symbol visible, the CLI tools still link the static core library, and a ctypes caller loads the dylib and synthesises through the Metal backend (device detected, output audio transcribes back to the input text).