Desktop Target

The desktop target compiles and runs the native binary selected from the shared client crate. Rekindle 0.1 supports desktop builds on x86_64-unknown-linux-gnu. Other native targets are not qualified and are rejected with a diagnostic instead of producing an untested release artifact.

Development

mix rekindle.dev builds the desktop target after client changes. Rekindle validates a successful build before replacing the running process. It then stops the current process, starts the candidate, and selects the candidate only after it remains running through the readiness interval. If the candidate fails and a retained executable exists, Rekindle makes one best-effort restart of that executable; the restart can also fail. A failed first launch has no previous executable to restore.

Run one build without starting the executable:

mix rekindle.build desktop

Production

mix rekindle.build desktop --release

The published layout is:

dist/rekindle/desktop/<rust-target>/application-<sha256>
dist/rekindle/desktop/<rust-target>/manifest.json

The manifest identifies the executable, Rust target, selected integration, Cargo package, binary, and content hash. A release build packages the executable but never launches it. Use the manifest from an application packager, installer, or deployment pipeline.

Rekindle does not bundle an Elixir runtime or application release into this artifact. An application that needs an embedded backend can compose the desktop artifact with its chosen Elixir distribution approach.