day-toolchain
One crate that knows where developer toolchains and SDKs live on your machine.
The Android SDK, NDK, and a usable JDK; Windows kits and C++/WinRT; the OpenHarmony NDK;
NSIS; rustup homes — every lookup checks the conventional environment variables first
(ANDROID_HOME, JAVA_HOME, and so on) and only then probes the places installers put
things. The day CLI, the backend build scripts, and generated projects all ask this
crate instead of hard-coding paths, so when a vendor moves something, there is one place
to fix it.
Part of Day
This crate is one piece of Day, a Rust framework for building apps
out of each platform's own widgets — AppKit, UIKit, Android's Material widgets, GTK 4, Qt 6,
XAML, and ArkUI — from one codebase. When you write button("Save"), macOS shows an
NSButton and Android shows a Material button. The framework also ships the tooling around
the app: the day CLI, a VS Code extension, GitHub CI workflows, localization,
accessibility, and dayscript automation.
New to Day? Start at daybrite.dev, or browse the source repository.