Neat to see more folks writing blogs on their experiences. This however does seem like it's an over-complicated method of building llama.cpp.
Assuming you want to do this iteratively (at least for the first time) should only need to run:
ccmake .
And toggle the parameters your hardware supports or that you want (e.g. if CUDA if you're using Nvidia, Metal if you're using Apple etc..), and press 'c' (configure) then 'g' (generate), then:
cmake --build . -j $(expr $(nproc) / 2)
Done.
If you want to move the binaries into your PATH, you could then optionally run cmake install.
Yeah the mingw method on windows is a ludicrous thing to even think about, and llama.cpp still has that as the suggested option in the readme for some weird reason. Endless sourcing of paths that never works quite right. I literally couldn't get it to work when I first tried it last year.
Meanwhile Cmake is like two lines and somehow it's the backup fallback option? I don't get it. And well on linux it's literally just one line with make.
Building anything on windows without cmake is just... I don't know why anyone would use anything else. I used to spend hours wrestling with build failures, but after setting up cmake, it just works with everything.
>Yeah the mingw method on windows is a ludicrous thing to even think about
Building most stuff on Windows is ludicrous, that's not something uncommon.
I've chosen MSYS there as it's the easiest and least paninful way of installing deps for Vulkan build.
Assuming you want to do this iteratively (at least for the first time) should only need to run:
And toggle the parameters your hardware supports or that you want (e.g. if CUDA if you're using Nvidia, Metal if you're using Apple etc..), and press 'c' (configure) then 'g' (generate), then: Done.If you want to move the binaries into your PATH, you could then optionally run cmake install.