Skip to content

v1.3.0

Choose a tag to compare

View all tags
@mohitsoni48 mohitsoni48 released this 22 Jun 10:32
· 40 commits to main since this release
v1.3.0
60374bc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

End-to-end engine builds — compile a CUDA llama.cpp (or any fork) from inside the app, downloading CUDA itself if you don't have it — plus each llama.cpp backend is now its own engine.

Added

  • 1-click build from source (Windows + CUDA). The build guide now compiles for you: clone → cmake configure → compile llama-server → bundle its CUDA runtime → auto-register + activate, with a live phase + streaming compiler log and a success screen. Builds with Ninja inside the MSVC dev environment (driving nvcc directly), so a standalone / conda CUDA works where the Visual Studio generator can't. Manual command path kept as a fallback.
  • Automatic CUDA download. No CUDA Toolkit? Click Download CUDA — TurboLLM fetches NVIDIA's official build components (nvcc + cudart + cuBLAS + headers, ~0.5 GB) and assembles a toolkit, picking a version your GPU driver supports. No NVIDIA installer, no account.
  • Self-contained builds. The built engine bundles the CUDA runtime DLLs next to its binary, so it runs even without a CUDA Toolkit on PATH.
  • Build environment (PATH override). CUDA / compiler in a conda env or custom path? Add that folder under Build environment and hit Re-check — those dirs are prepended to PATH for both detection and the build.
  • One-click rebuild. The "newer source available" chip on source-built engines recompiles at the latest commit in place.

Changed

  • Compile-from-source is no longer guidance-only; the prerequisite checker and the build both honor the configured toolchain dirs.
  • Each llama.cpp backend is its own engine. CUDA, ROCm, CPU, Vulkan and SYCL builds now appear individually — switch between them (and TurboQuant, forks, …) straight from the Running now dropdown, with no per-row "Use" button. The recommended backend sits in Install & manage; the rest live in a collapsible Other llama.cpp builds section. Multiple builds of one backend collapse into that engine, newest first.

Fixed

  • Updating / managing a llama.cpp backend no longer claims it's "not installed." A backend updated to a newer build than the bundled default was wrongly reported as missing — so Update could fail, or re-download a duplicate. Backend install state is now resolved by what's actually on disk, regardless of build number; deleting a backend cleans up all of its builds.

Full changelog: https://github.com/mohitsoni48/Turbo-LLM/blob/main/turbollm/CHANGELOG.md

Assets 2
Loading