This repository automatically builds and publishes Python wheels for abetlen/llama-cpp-python across all major platforms and architectures using GitHub Actions and cibuildwheel.
β Wheels are uploaded to the GitHub Releases section of this repo β ready to download!
This build system supports:
| OS | Architecture |
|---|---|
| Linux | x86_64, aarch64 |
| macOS | arm64, x86_64 |
| Windows | x86_64 |
Wheels are built for:
This means all of the following tags will be available:
cp38,cp39,cp310,cp311,cp312,cp313
watch-upstream.yml β Scheduled Trigger (Every 12h)v0.3.14 from v0.3.14-cu124)If the release hasnβt been built yet:
build-wheels.yml with that versionbuild-wheels.yml β Cross-Platform Buildercibuildwheel and docker buildx to build wheelsSupports:
aarch64)llama_cpp_python-0.3.14-cp38-cp38-manylinux_x86_64.whl
llama_cpp_python-0.3.14-cp310-cp310-manylinux_aarch64.whl
llama_cpp_python-0.3.14-cp313-cp313-macosx_11_0_arm64.whl
llama_cpp_python-0.3.14-cp311-cp311-win_amd64.whl
You can manually build a specific version:
Actions tabbuild-wheels.ymlv0.3.14-cu124)The watch-upstream.yml workflow runs every 12 hours via cron:
schedule:
- cron: '0 */12 * * *' # Every 12 hours
All built .whl files are published as release assets under the Releases tab for the corresponding version tag.
cibuildwheelQ: Does this build support CUDA or Metal?
A: Currently, only CPU-only builds are supported. CUDA and Metal require custom runners and are not compatible with GitHub-hosted environments.
Q: Why do wheels include cu124 in the tag?
A: That part comes from the upstream release tag. We extract the base tag (e.g., v0.3.14) for organizing releases.
Q: How do I change supported Python versions?
A: Edit the CIBW_BUILD value in build-wheels.yml. This repo is already set to build for Python 3.8β3.13.
MIT Β© eswarthammana β Built on top of open source contributions from abetlen and pypa/cibuildwheel.