GitLab

Make CPU builds parallel and customizable AMD GPUs

Probe GPUs before backend init

Detect potential error scenarios so we can fallback to CPU mode without
hitting asserts.

The linux build now support parallel CPU builds to speed things up.
This also exposes AMD GPU targets as an optional setting for advaced
users who want to alter our default set.

Combine the 2 Dockerfiles and add ROCm

This renames Dockerfile.build to Dockerfile, and adds some new stages
to support 2 modes of building - the build_linux.sh script uses
intermediate stages to extract the artifacts for ./dist, and the default
build generates a container image usable by both cuda and rocm cards.
This required transitioniing the x86 base to the rocm image to avoid
layer bloat.

More WSL paths

Switch to local dlopen symbols

Fix CPU-only build under Android Termux enviornment.

Update gpu.go initGPUHandles() to declare gpuHandles variable before
reading it. This resolves an "invalid memory address or nil pointer
dereference" error.

Update dyn_ext_server.c to avoid setting the RTLD_DEEPBIND flag under
__TERMUX__ (Android).

fix show handler

api: add model for all requests

ci: update setup-go action

prefer using req.Model and fallback to req.Name

Mechanical switch from log to slog

install: pin fedora to max 37

A few obvious levels were adjusted, but generally everything mapped to "info" level.

Updated readme with the web link for haystack ollama integration

Let gpu.go and gen_linux.sh also find CUDA on Arch Linux

Refine the linux cuda/rocm developer docs

Add multiple CPU variants for Intel Mac

The runners are x86 so we can only run binaries that match.

This also refines the build process for the ext_server build.

fix: normalize name path before splitting

Bump llama.cpp to b1842 and add new cuda lib dep

Upstream llama.cpp has added a new dependency with the
NVIDIA CUDA Driver Libraries (libcuda.so) which is part of the
driver distribution, not the general cuda libraries, and is not
available as an archive, so we can not statically link it.  This may
introduce some additional compatibility challenges which we'll
need to keep an eye on.