Skip to content
KataglyphisPublic

About

🦀 My collecrion of various best practices and how to's for Rust 🦀

Topics

Resources

Stars

4 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,167 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OxidANT logo: a rusted ant inside a gear

OxidANT

The Kataglyphis family's Rust crates and the Rust best practices they follow.

Linux x64 · build + test Linux arm64 · build + test Linux riscv64 · cross build + test Windows x64 · build + test Linux NVIDIA GPU candidates Linux AMD GPU candidate Windows GPU candidates Windows arm64 · cross build + test CodeQL TopLang Donate Twitter

A push to develop and every PR run Linux x64; the other lanes run on request and before a release, so a lane's badge shows its runs started by hand and a requested run is listed under On request (docs/ci.md). PowerShell lint stays strict, and the separate quality workflow uploads a complexity report on each push and PR; its manual strict input tests the current complexity debt.

Docs site

OxidANT is the Kataglyphis family's Rust workspace: the crates two other repositories build as a submodule, plus the Rust practices, gates and packaging they all inherit. OmniAccelerANT calls the root package through flutter_rust_bridge and ships ObservANT, the cat cam; BeschleunigerBallett links the cxx bridge crate through Corrosion and builds the WebGPU renderer. It started as a project template and that scaffolding is still here, but the crates are real code with real consumers.

Dependency updates: run bash scripts/linux/renovate-local.sh to report, --apply --dry-run to plan, and --apply to update. CI checks the wrapper and config; see the shared Renovate guide. The Burn demos use Flex; the documented Burn patch keeps their unused legacy Torch backend and its vulnerable ZIP/Zstd chain out of the lockfile.

Highlights

  • ObservANT (crates/observant): camera, cat detection, WebRTC stream and web page in one service; its shared producer container helper also serves OmniAccelerANT's bundle packager.
  • A WebGPU glTF renderer, native and in the browser: PBR with IBL, shadows, SSAO, bloom, golden tests.
  • ONNX inference on the family's chain-built ONNX Runtime (CPU, DirectML, CUDA), with tract as its fallback.
  • No feature flags: every build carries everything its target can run.
  • GStreamer capture, a wgpu GUI overlay with FPS, latency and CPU, and a GTK4 camera GUI on Linux.
  • Five build lanes: Linux x64, arm64 and riscv64, Windows x64 and arm64.
  • Packages that carry their own GStreamer, ONNX Runtime, model and project license: tar, deb, AppImage and flatpak on Linux; portable zip, MSI and MSIX on Windows. Linux packages verify the matched ONNX wheel's license and notices; Windows uses the project icon and generates the MSI's RTF from the project license.

GPU package candidates

On demand: Linux NVIDIA x64/arm64, Linux AMD x64, and Windows NVIDIA/AMD x64. Open a successful run and download its matching artifact under Artifacts (sign-in required). Linux candidates contain tar, DEB and AppImage; Windows candidates are portable ZIPs. They are experimental, separate from releases and require matching host GPU drivers and runtimes. The current infrastructure pin blocks the workflows; see packaging for prerequisites and verification status. CPU packages remain available through the existing lanes. The NVIDIA and Windows candidate workflows also accept reusable workflow calls; GPU profiling remains opt-in and does not promote their artifacts to releases. The Linux NVIDIA architecture input defaults to both architectures and can select x64 or arm64 alone. For Linux AMD x64 and NVIDIA x64/arm64, promote-verified is disabled until CPU and GPU detector output parity is checked. GPU operator profiling remains available with verify-gpu; its results alone do not make a candidate verified.

Quick start

git clone --recurse-submodules --branch develop https://github.com/Kataglyphis/OxidANT.git
cd OxidANT
cargo build --workspace --locked

Prerequisites, the API docs and Linux containers locally: docs/getting-started.md.

Documentation

Topic Read
Getting started docs/getting-started.md
The crates, what each target builds, and the consumers docs/crates.md
Language models: the chain GenAI or an endpoint, the CLI, the Flutter bridge docs/text.md
Tests, lints and the GPU tests docs/testing.md
Running the CLI, the GUI and the demos docs/running.md
ObservANT, the cat cam docs/observant.md
Windows: shared source selection, config, build, test and arm64 source fixtures docs/windows.md
Packages: Linux tar, deb, AppImage, flatpak; Windows MSIX and MSI docs/packaging.md
Continuous integration, lane by lane docs/ci.md
Dependency updates docs/updates.md
The WebGPU renderer crates/webgpu_renderer/README.md
Shader ownership and regeneration docs/shaders.md
API docs (rustdoc) rust.jonasheinle.de
Rules for agents and contributors, CI AGENTS.md
Known work BACKLOG.md
Changes CHANGELOG.md

Contributing and contact

OxidANT is one of the Kataglyphis repositories, which share one way to contribute and one contact. Licence: MIT, see LICENSE.

About

🦀 My collecrion of various best practices and how to's for Rust 🦀

Topics

Resources

Stars

4 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

Generated from Kataglyphis/template