installrs 0.1.0-rc9

Build self-contained software installers in plain Rust, with an optional native wizard GUI (Win32 / GTK3), component selection, progress, cancellation, and compression.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# AGENTS.md

Guidance for AI coding tools working on this project.

@README.md
@docs/getting-started.md
@docs/architecture.md

## Commands

```bash
# Build library and binary
cargo build --release

# Run tests
cargo test

# Check without building
cargo check

# Lint - always run before committing
cargo clippy

# Cross-check the Win32 backend from Linux (requires gcc-mingw-w64-x86-64
# and `rustup target add x86_64-pc-windows-gnu`)
cargo clippy --features gui-win32 --target x86_64-pc-windows-gnu

# Format - always run before committing
cargo fmt

# Build an installer using the CLI (from an installer source directory)
installrs --target ./my-installer --output installer

# Build against the working-tree runtime (not the published crate) —
# set this for InstallRS-on-InstallRS development.
INSTALLRS_LOCAL_PATH=1 installrs --target ./my-installer --output installer

# Verbose / trace output
installrs --target ./my-installer -v    # debug
installrs --target ./my-installer -vv   # trace
```

## Keeping docs in sync

When you change code that affects how someone uses or understands
InstallRS, update README.md and/or the relevant doc files in `docs/`.
Make sure to update documentation indexes and links.
If you add a new doc file, add it to any relevant indexes
and link to it from the README and any relevant "See also" doc sections.
Also update `CHANGELOG.md` with a brief high-level overview note about the change.
Keep changelog entries concise and focused on the user-facing impact of the change;
don't include internal implementation details or development notes.