Skip to content

feat(cuda): add LLamaSharp.Backend.Cuda13 packages - #1441

Open
modelpath-dev wants to merge 3 commits into
SciSharp:masterfrom
modelpath-dev:feat/1360-cuda13-nuget
Open

modelpath-dev wants to merge 3 commits into
SciSharp:masterfrom
modelpath-dev:feat/1360-cuda13-nuget

Conversation

@modelpath-dev

@modelpath-dev modelpath-dev commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

Why

Part 3 of the CUDA 13 split for #1360. Ships the Backend.Cuda13 nuspecs, Runtime.targets copy rules for cu13.0.0, and package docs. Hold this until the NuGet ownership issue Martin mentioned is resolved and cuda13 binaries exist from part 1.

Depends on #1440.

Scope

  • LLama/runtimes/build/LLamaSharp.Backend.Cuda13*.nuspec
  • LLama/LLamaSharp.Runtime.targets copy-to-output links for cu13.0.0 → cuda13
  • README.md, docs/QuickStart.md package mentions

Out of scope: compile workflow and NativeLibraryWithCuda (parts 1 and 2).

Tradeoffs

Runtime.targets sits with the NuGet packaging change, not the loader, because it is copy-to-output packaging for deps, not Prepare() probe logic.

Blast Radius

Adds new packages and optional copy rules gated on Exists(...). Existing Cuda12 packages and paths are untouched. Publishing still waits on package ownership.

Verification

  • NuGet-only files vs the loader tip: targets, three nuspecs, README, QuickStart.
  • Full tip patch-id matches the pre-split combined change that used to live on this stack.
  • No local pack run (needs binaries from Compile). Review against the Cuda12 nuspec/targets pattern.

Extend the cublas matrix and Gather Binaries layout so a Compile run can produce cu13.0.0 artifacts next to cu12.4.0 without changing the managed loader or NuGet packages yet.
Teach NativeLibraryWithCuda to try major 13 when SkipCheck is on or the detected major is 13, and cover the path order with unit tests. Binaries and NuGet packages stay out of this change.
Ship the Cuda13 nuspecs, Runtime.targets copy rules for cu13.0.0 deps, and the README/QuickStart package mentions. Safe to land after binaries exist and the nuget ownership issue is resolved.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant