From 724cd3d64e3c12412470d033b1ff73f037c3fb9c Mon Sep 17 00:00:00 2001 From: Oliver Hamlet Date: Fri, 9 Jan 2026 21:10:54 +0000 Subject: [PATCH] Update downloads info in readme --- README.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index b4ecc6e6..9bc70e74 100644 --- a/README.md +++ b/README.md @@ -11,21 +11,22 @@ LOOT also provides some load order error checking, including checks for requirem libloot provides access to LOOT's metadata and sorting functionality, and the LOOT application is built using it. -libloot's core is written in Rust, and C++, Python and Node.js wrappers can be found in the `cpp`, `python` and `nodejs` subdirectories respectively. +libloot is written in Rust. C++, Python and Node.js wrappers can be found in the `cpp`, `python` and `nodejs` subdirectories respectively. ## Downloads -Binary artifacts are currently only provided for the C++ wrapper. +libloot releases are published to [crates.io](https://crates.io/crates/libloot). -Releases are hosted on [GitHub](https://github.com/loot/libloot/releases). +The C++ wrapper is available as a prebuilt shared library: -Snapshot builds are available as artifacts from [GitHub Actions runs](https://github.com/loot/libloot/actions), though they are only kept for 90 days and can only be downloaded when logged into a GitHub account. To mitigate these restrictions, snapshot build artifacts include a GPG signature that can be verified using the public key hosted [here](https://loot.github.io/.well-known/openpgpkey/hu/mj86by43a9hz8y8rbddtx54n3bwuuucg), which means it's possible to re-upload the artifacts elsewhere and still prove their authenticity. +- Release binaries are hosted on [GitHub](https://github.com/loot/libloot/releases), and are only available for 64-bit Windows. +- Snapshot builds are available for 64-bit Windows and 64-bit Linux, as artifacts from [GitHub Actions runs](https://github.com/loot/libloot/actions). The snapshot build artifacts are named like so: -The snapshot build artifacts are named like so: + ``` + libloot---g_-. + ``` -``` -libloot---g_-. -``` + GitHub Actions only keeps artifacts for 90 days, and they can only be downloaded when logged into a GitHub account. To mitigate these restrictions, snapshot build artifacts include a GPG signature that can be verified using the public key hosted [here](https://loot.github.io/.well-known/openpgpkey/hu/mj86by43a9hz8y8rbddtx54n3bwuuucg), which means it's possible to re-upload the artifacts elsewhere and still prove their authenticity. ## Build