cargo-bundle
github.com
Spec sheet
- Purpose
- cargo-bundle generates installers or app bundles for GUI executables built with Cargo.Read 11 Oct 2026 · github.com
- License
- The project is licensed under either Apache Software License or MIT License.Read 11 Oct 2026 · github.com
- Maker
- The GitHub profile identifies the maker as George Burton; it does not state a headquarters or founding date.Read 11 Oct 2026 · github.com
- App metadata
- Configuration supports fields such as app name, identifier, icons, version, resources, copyright, category, and descriptions.Read 11 Oct 2026 · github.com
- AppImage limitation
- The README says shared libraries are not automatically collected for AppImage bundles, so dynamically linked GUI apps may need matching system libraries or staged libraries.Read 11 Oct 2026 · github.com
- Configuration
- Projects configure bundle metadata in a `[package.metadata.bundle]` section of Cargo.toml, including fields such as name, icon, description, and copyright.Read 11 Oct 2026 · github.com
- Cross-compilation
- It supports selecting a target with `--target`, and macOS can combine architectures into a universal binary.Read 11 Oct 2026 · github.com
- Existing binaries
- The `--binary-path` option packages an already-built executable without rebuilding it, and the input file is copied rather than modified.Read 11 Oct 2026 · github.com
- Experimental platforms
- The README says iOS and Windows support is experimental.Read 11 Oct 2026 · github.com
- Formats
- It can produce macOS .app bundles, Linux .deb and .AppImage packages, and Windows .msi installers.Read 11 Oct 2026 · github.com
- Installation
- The README says to install it with `cargo install cargo-bundle`, which adds it as a subcommand to Cargo.Read 11 Oct 2026 · github.com
- License and stability
- The repository README describes the project as very early alpha and says its bundle metadata format may change without a stability guarantee; it lists MIT or Apache licensing.Read 11 Oct 2026 · github.com
- Linux limitation
- The README says AppImage creation does not automatically collect shared libraries, so dynamically linked GUI apps may require matching system libraries or staged libraries.Read 11 Oct 2026 · github.com
- Linux output
- It can create .deb packages and .AppImage bundles for Linux.Read 11 Oct 2026 · github.com
- macOS and iOS output
- It can create .app bundles for macOS and iOS, with iOS support described as experimental.Read 11 Oct 2026 · github.com
- Notarization
- The README says Apple artifacts are signed but not notarized by cargo-bundle.Read 11 Oct 2026 · github.com
- Pending formats
- The README says support for Linux .rpm packages and Android .apk packages is still pending.Read 11 Oct 2026 · github.com
- Prebuilt executables
- The `--binary-path` option packages an already-built executable without running `cargo build` again.Read 11 Oct 2026 · github.com
- Signing
- The README describes optional Apple bundle and DMG signing, optional Windows Authenticode signing, and configurable keyless Sigstore signing for Linux artifacts.Read 11 Oct 2026 · github.com
- Signing limitation
- The README says Apple artifacts are not notarized, and Windows signing requires the opt-in `windows-signing` feature, which links a GPL-3.0-or-later implementation.Read 11 Oct 2026 · github.com
- Stability
- The README labels the project “Very early alpha” and says the bundle metadata format may change with no guarantee of stability.Read 11 Oct 2026 · github.com
- Windows output
- It can create .msi installers for Windows, whose support is described as experimental.Read 11 Oct 2026 · github.com
Where Specifiction places it
- Software Packaging Tools#7 of 297.9