Windows install method: Llama.cpp in scoop

[mathijshenquet]

I recently helped merge llama.cpp support into Scoop, the Windows package manager. See this pull request: ScoopInstaller/Versions#2295.

Current Implementation

The packages have been added to the 'Versions' bucket with all variants from the GitHub releases available. Users can now install specific builds:

scoop install versions/llama.cpp-cpu     # CPU version (AMD64 or ARM64)
scoop install versions/llama.cpp-cu117   # CUDA 11.7 support
scoop install versions/llama.cpp-cu124   # CUDA 12.4 support
scoop install versions/llama.cpp-hip-gfx1030  # HIP (GFX1030)
scoop install versions/llama.cpp-hip-gfx1100  # HIP (GFX1100)
scoop install versions/llama.cpp-hip-gfx1101  # HIP (GFX1101)
scoop install versions/llama.cpp-opencl  # OpenCL version
scoop install versions/llama.cpp-sycl    # SYCL version
scoop install versions/llama.cpp-vulkan  # Vulkan version

Executables Provided

Upon installation, the following executables are added to the user's PATH:

llama-batched-bench.exe
llama-bench.exe
llama-cli.exe
llama-gemma3-cli.exe
llama-gguf-split.exe
llama-imatrix.exe
llama-llava-cli.exe
llama-minicpmv-cli.exe
llama-mtmd-cli.exe
llama-perplexity.exe
llama-quantize.exe
llama-qwen2vl-cli.exe
llama-run.exe
llama-server.exe
llama-tokenize.exe
llama-tts.exe

Proposal for Enhancement

I propose updating the following files with Scoop installation instructions.

• ./README.md
• ./docs/install.md

If concensus is reached I would be willing to make PR for this if desired.

Question

Is the above list of executables correct and stable? I noticed recent changes to the executable list. It's important that this remains in sync with the project.

Alternatively, Scoop allows a different installation method where a PATH entry is added instead of enumerating each executable, however this is not so desirable as llama.cpp also includes non llama-* executable.

We could also enumerate a smaller list of stable exeuctables which most users would use, eg at least llama-cli and llama-server.

[slaren]

I am working at the moment on building packages for winget. Uploading the packages to other repositories as well would be great, but we should try to use the same packages for all repositories to avoid confusion. My goal for winget is to create a single package that contains the most important backends and can automatically choose which ones to use at runtime. Please give me some time to finish this so that we can use the same approach before we start advertising these packages in the documentation.

[mathijshenquet]

Sure! Feel free to ping me and I will be glad to assist for scoop packages!