hugo/RuDS
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Package statically linked ONNX runtimes correctly.
Some checks failed
Tagged release / prepare-release (push) Successful in 3m1s
Details
Tagged release / build-linux-x64 (push) Successful in 36m15s
Details
Tagged release / build-macos (push) Failing after 24m59s
Details
Tagged release / build-linux-arm64 (push) Successful in 34m54s
Details
Tagged release / build-windows (push) Failing after 30m33s
Details
Tagged release / publish-release (push) Has been skipped
Details

Browse Source
This commit is contained in:
Hermes Agent
2026-08-14 22:18:59 +00:00
parent f59fd03ad2
commit 612f4f71df
2 changed files with 4 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -35,7 +35,7 @@ RuDS uses no JavaScript application runtime and loads no CSS or JavaScript from
The packaged Apple Silicon application requires macOS 26 or newer.
Packaged executables share native `bds-core` and `bds-server` dynamic libraries. Release archives also carry the matching ONNX Runtime library; Windows archives include Microsoft's DirectML redistributable and its license for GPU-accelerated local embeddings. The **Install CLI** action replaces `~/.local/bin/bds-cli` with a symbolic link to the packaged CLI, so the command executes beside the same runtime libraries and always follows the package selected by the latest installation.
Packaged executables share native `bds-core` and `bds-server` dynamic libraries. macOS and Linux link ONNX Runtime statically into `bds-core`; Windows archives carry the matching ONNX Runtime DLL plus Microsoft's DirectML redistributable and license for GPU-accelerated local embeddings. The **Install CLI** action replaces `~/.local/bin/bds-cli` with a symbolic link to the packaged CLI, so the command executes beside the same runtime libraries and always follows the package selected by the latest installation.
Local macOS packages are ad-hoc signed without hardened runtime. A Developer ID and notarization remain optional release-channel steps for downloads that should pass Gatekeeper without a user override.