cargo-crapapp
Cargo plugin for bundling multiplatform Rust apps from CRAP.toml.
It exists because some enterprise environments, especially in banking, are very good at inventing security rituals and very bad at understanding what is actually secure. Sometimes Artifactory is missing, nobody owns Linux package distribution, Windows packaging tools are blocked or are piece of sh*t.
The goal is simple: read a manifest, build Rust binaries for configured targets, and produce something a user can install without negotiating with five teams and producing 2534 Jira tickets.
Status
Finished
- Basic
setup.exegeneration for Windows from the CLI. - Cargo package and feature selection from
CRAP.toml. - Windows payload embedding into
setup.exe. - Embedded
uninstall.exe. - Per-user Windows uninstall registry entry.
- Per-user
PATHupdates throughHKCU\Environment. - Installer-time
ADD_TO_PATHvariable for PATH updates. - Windows icon wiring for configured app binaries and uninstall registry display icons.
- Microsoft Fluent icons for generated setup/uninstall executables.
inspectcommand with text and JSON output.
Unfinished
- Building self-contained apps for macOS.
- Building self-contained apps for Linux.
- Real packaging formats for Linux/macOS.
- Proper end-to-end tests across all supported targets.
Planned
- Installation and uninstallation GUI for Windows.
- Signing Windows apps.
- Better output directory structure.
- More validation around installer paths and payload layout.
Example
[]
= "Example Publisher"
= ["example"]
= []
[]
= [
"x86_64-pc-windows-gnu",
]
= "$INSTALLPATH"
= [
{ = "Cargo.toml", = "manifests/Cargo.toml" },
]
Windows setup variables are passed with repeated --args KEY=value flags:
Inspect the generated build manifest:
Build configured targets:
Windows output currently lands in:
.crapapp_build/windows/<target>/setup.exe
Why So Small?
Because this tool is not trying to become another sacred enterprise platform. It should stay boring, inspectable, and easy to delete when something better is available.
The design bias is:
- no mystery services
- no central server
- no required admin registry writes
- no shell profile hacks
- no pretending that packaging is more magical than copying files carefully
Should You Use It?
Probably not. The only reason to use it is that your life circles in a corporate trap and normal packaging tools are politically unavailable.