Michael Yang dcfb7a105c next build (#8539) 3 mēneši atpakaļ
..
llama.cpp dcfb7a105c next build (#8539) 3 mēneši atpakaļ
patches dcfb7a105c next build (#8539) 3 mēneši atpakaļ
runner 1deafd8254 llama: update vendored code to commit 46e3556 (#8308) 3 mēneši atpakaļ
.gitignore 96efd9052f Re-introduce the `llama` package (#5034) 6 mēneši atpakaļ
README.md dcfb7a105c next build (#8539) 3 mēneši atpakaļ
build-info.cpp 7a81daf026 llama: update vendor code to commit ba1cb19c (#8101) 4 mēneši atpakaļ
llama.go dcfb7a105c next build (#8539) 3 mēneši atpakaļ
llama_test.go 61676fb506 llama: move grammar tests to llama_test.go (#8411) 3 mēneši atpakaļ
mllama.cpp 527cc97899 llama: update vendored code to commit 40c6d79f (#7875) 4 mēneši atpakaļ
mllama.h c7cb0f0602 image processing for llama3.2 (#6963) 6 mēneši atpakaļ
sampling_ext.cpp 1deafd8254 llama: update vendored code to commit 46e3556 (#8308) 3 mēneši atpakaļ
sampling_ext.h 1deafd8254 llama: update vendored code to commit 46e3556 (#8308) 3 mēneši atpakaļ
vendoring 1deafd8254 llama: update vendored code to commit 46e3556 (#8308) 3 mēneši atpakaļ

README.md

llama

This package provides Go bindings to llama.cpp.

Vendoring

Ollama vendors llama.cpp and ggml. While we generally strive to contribute changes back upstream to avoid drift, we carry a small set of patches which are applied to the tracking commit.

If you update the vendoring code, start by running the following command to establish the tracking llama.cpp repo in the ./vendor/ directory.

make -f Makefile.sync apply-patches

Updating Base Commit

Pin to new base commit

To change the base commit, update FETCH_HEAD in Makefile.sync.

When updating to a newer base commit, the existing patches may not apply cleanly and require manual merge resolution.

Start by applying the patches. If any of the patches have conflicts, the git am will stop at the first failure.

make -f Makefile.sync apply-patches

If there are conflicts, you will see an error message. Resolve the conflicts in ./vendor/, and continue the patch series with git am --continue and rerun make -f Makefile.sync apply-patches. Repeat until all patches are successfully applied.

Once all patches are applied, commit the changes to the tracking repository.

make -f Makefile.sync format-patches sync

Generating Patches

When working on new fixes or features that impact vendored code, use the following model. First get a clean tracking repo with all current patches applied:

make -f Makefile.sync clean apply-patches

Iterate until you're ready to submit PRs. Once your code is ready, commit a change in the ./vendor/ directory, then generate the patches for ollama with

make -f Makefile.sync format-patches

In your ./vendor/ directory, create a branch, and cherry-pick the new commit to that branch, then submit a PR upstream to llama.cpp.

Commit the changes in the ollama repo and submit a PR to Ollama, which will include the vendored code update with your change, along with the patches.

After your PR upstream is merged, follow the Updating Base Commit instructions above, however first remove your patch before running apply-patches since the new base commit contains your change already.