commit 118f3bd6db1bc4aabf3b2b4428214a1b3ebe2976
Author: Liav Mordouch <liavmordouch@gmail.com>
Date: Thu Apr 30 20:44:33 2026 +0300

fix(deadlock-modmanager): build with tauri/custom-protocol feature

Tauri's generate_context!() macro picks between the embedded
frontendDist bundle and the devUrl dev server based on
`cfg!(not(feature = "custom-protocol"))`. The official tauri-cli
enables this feature implicitly, but bare `cargo build` does not -
so the release binary was baking in http://localhost:1420 and the
WebView failed at launch with "Could not connect to localhost:
Connection refused".

Pass `--features tauri/custom-protocol` to both `cargo build` and
the final `cargo rustc` link step so the embedded frontend bundle
is actually used.

Also realign the -9999 live ebuild with the proven 0.18.0 recipe
(pnpm ui:build, two-stage cargo build/rustc, GNU toolchain, manual
ring/unrar/bz2/c++ link args, perl + nasm BDEPEND).

commit 8020b12e1ea1b8d0debde01145850582fa85e3a8
Author: Liav Mordouch <liavmordouch@gmail.com>
Date: Thu Apr 30 20:20:56 2026 +0300

games-util/deadlock-modmanager: build the Vite frontend bundle

Without running `pnpm ui:build` before `cargo build`, Tauri has no
`apps/desktop/dist/` to embed via `frontendDist`, so it bakes in
the dev server URL and the resulting binary fails at runtime with
"Could not connect to localhost: Connection refused". Build the
frontend explicitly between `pnpm install` and the cargo invocation.

commit a9587337dac55937711437d97972a06bbe0cce2d
Author: Liav Mordouch <liavmordouch@gmail.com>
Date: Thu Apr 30 20:16:50 2026 +0300

games-util/deadlock-modmanager: bump to 0.18.0

Upstream renamed the project (and GitHub org) from
Stormix/deadlock-modmanager to deadlock-mod-manager/deadlock-mod-manager,
so the tarball top-level directory is now deadlock-mod-manager-$.
Adjust S accordingly while keeping the overlay PN as
deadlock-modmanager for continuity.

Build workarounds for rustc 1.95 + ring 0.17.14 + unrar_sys 0.5.8:

* Force GNU bfd ld - bundled rust-lld cannot resolve ring's
perlasm-generated symbols.
* Two-stage build (cargo build then cargo rustc --bin) so extra
link arguments apply only to the leaf binary, avoiding leakage
to host build scripts and dependency target dylibs.
* Manually pass -lring_core_0_17_14_ and -lunrar - cargo no
longer propagates these static-lib directives to the final
link line even though it propagates the matching -L paths.
* Link against libc++ (provided by dev-libs/libcxx) and libgcc:
unrar_sys' build.rs passes -stdlib=libc++ via flag_if_supported,
which gcc-15 also accepts, so libunrar.a ends up with libc++
ABI symbols regardless of compiler choice.

commit c3bdb9917963eefd2c299763bb7012715cb9b7fc
Author: Liav Mordouch <liavmordouch@gmail.com>
Date: Wed Apr 29 20:34:28 2026 +0300

feat(games-util): add deadlock-modmanager