Platforms and performance

Downloads#

Controllers work in the GUI on Windows, macOS, Linux and PortMaster. install-launcher works on Windows and Linux.

Building it yourself#

cargo install dream-ini

That builds the desktop program, GUI included. Other shapes are a matter of Cargo features:

The release builds are exactly these:

A program that only wants the importer depends on the library without the GUI:

[dependencies]
dream-ini = { version = "0.4", default-features = false }

Signed releases#

Each release archive holds, beside the program, a Sigstore bundle for it, such as dream-ini-Linux-X64.bundle, made by StroggForge’s release workflow. It proves that workflow built the program for this repository:

cosign verify-blob dream-ini \
  --bundle dream-ini-Linux-X64.bundle \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp '^https://github.com/DreamWeave-MP/StroggForge/\.github/workflows/rustGlobalBuild\.yml@' \
  --certificate-github-workflow-repository DreamWeave-MP/dream-ini

Each GitHub release also links every archive’s VirusTotal scan.

License#

MIT OR Apache-2.0, at your option, since 0.3.1. 0.1.0 and 0.2.0 were GPL-3.0-only.

What is tested#

Every push runs StroggForge’s release workflow: the tests with every feature on Windows, Linux and macOS on both Apple silicon and Intel, Clippy at the pedantic level with warnings as errors, rustfmt, and cargo audit, before anything is built for release.

The tests import real files: INIs with each edge of the GameFile and Archive rules, cfgs with comments, relative paths, symbolic links and config= chains, and every output mode through the built program. The Luau tests type-check the extension’s definitions with Luau’s own checker, run a strict script against them, and drive every function.

What an import costs#

cargo bench --bench round_trip imports a large synthetic install: 4226 INI entries in 1543 sections, a 514-entry cfg, 129 archives and 256 data= folders that no longer exist. Medians on one quiet machine, release build:

0.4.0 is faster because it no longer probes search paths that are not folders, and resolves the cfg’s data= folders once per import instead of once per file found.

From Luau, cargo bench --features luau --bench luau_boundary runs each function from a frozen script on the same install. Medians, against the mlua binding it replaced in 0.4.0, both over 0.3.1’s importer:

The binding costs about what it did; the import is what got faster. With 0.4.0’s importer, importPaths on this install takes 4.87 ms.