Conversation
|
A bunch of breakage here... Android, MacOS and Windows builds all fail. |
|
Android: I originally introduced aarch64-linux-android builds on utilityai/llama-cpp-rs#605 In a later PR, utilityai/llama-cpp-rs#629 , this manual The recent PR utilityai/llama-cpp-rs#861 introduces a |
|
The android fix PR is up: utilityai/llama-cpp-rs#872 Pointed this repo towards the branch on our fork of llama-cpp-rs, just to show that it actually does fix the android builds. |
|
MacOS: It seems like that macos build failure likely wasn't caused by changes in llama-cpp-rs, but rather by some funky stuff with our github actions caching (which wasn't doing much anyway). @s194042 ran into the same issue and removed the macos caching in commit 3c1d8a5 Rebasing this branch on main should do it. (regardless, the caching-induced failure seems flaky- can't easily reproduce) |
ed8a474 to
8127a11
Compare
* add some diagnostics to windows build * temporarily disable non-windows builds for faster testing in CI * try to skip cmake install to see how llama builds react * more windows build configuration wankery * only make tmp dir if not exists * remove custom temp dir, possibly dodging the ggml-cpu.lib install error * remove a bunch of config to reproduce original error * try using ninja as the cmake generator * clean up after debugging windows build issue
|
Windows: The windows thing was the latest (and maybe last? 🎉) chapter of a long-standing issue. It's a mess of nested CMakeLists.txt files, that include each other via ExternalProject_Add. |
01a0ce8 to
2305ff8
Compare
...does what it says on the tin.