Code change:
<ins> { stdenv , lib , fetchFromGitHub , fetchpatch , meson , ninja , pkg-config , python3Packages , dbus , glslang , libglvnd , libXNVCtrl , mesa , vulkan-headers , vulkan-loader , xorg }: stdenv.mkDerivation rec { pname = "mangohud${lib.optionalString stdenv.is32bit "_32"}"; version = "0.4.1"; src = fetchFromGitHub { owner = "flightlessmango"; repo = "MangoHud"; rev = "v${version}"; sha256 = "04v2ps8n15ph2smjgnssax5hq88bszw2kbcff37cnd5c8yysvfi6"; fetchSubmodules = true; }; patches = [ (fetchpatch { # FIXME obsolete in >=0.5.0 url = "https://patch-diff.githubusercontent.com/raw/flightlessmango/MangoHud/pull/208.patch"; sha256 = "1i6x6sr4az1zv0p6vpw99n947c7awgbbv087fghjlczhry676nmh"; }) ]; mesonFlags = [ "-Dappend_libdir_mangohud=false" "-Duse_system_vulkan=enabled" "--libdir=lib${lib.optionalString stdenv.is32bit "32"}" ]; buildInputs = [ dbus glslang libglvnd libXNVCtrl mesa python3Packages.Mako vulkan-headers vulkan-loader xorg.libX11 ]; nativeBuildInputs = [ meson ninja pkg-config python3Packages.Mako python3Packages.python ]; preConfigure = '' mkdir -p "$out/share/vulkan/" ln -sf "${vulkan-headers}/share/vulkan/registry/" $out/share/vulkan/ ln -sf "${vulkan-headers}/include" $out ''; meta = with lib; { description = "A Vulkan and OpenGL overlay for monitoring FPS, temperatures, CPU/GPU load and more"; homepage = "https://github.com/flightlessmango/MangoHud"; platforms = platforms.linux; license = licenses.mit; maintainers = with maintainers; [ zeratax ]; }; } </ins>

Related discussion:
text: Project description A modification of the Mesa Vulkan overlay. Including GUI improvements, temperature reporting, and logging capabilities. Metadata homepage URL: source URL: license: gpl3 platforms: linux
I tried myself at this and have a working package now for NUR based on But I haven't yet figured out how to create a 32 and 64-bit version. Depending on the game both are necessary. To just get a 32bit version I currently just use: instead of just
It might make sense to just build the 32bit and 64bit packages separately and then merge them together in a wrapper.
okay I did something similar, though not with a wrapper which is probably a little hackish I am not sure: but this allows me now to use mangohud with 64 and 32 bit applications
That seems like a reasonable solution, although it is a little bit hackish. I'm running into a similar issue with , and it's not really clear what the best approach is. recommended keeping the two builds separate for vkBasalt. However, to ensure we can install both builds we would have to do extra patching, and use separate names for the 32bit and 64bit build. Users might also expect to have both builds in one package like on other distros. I'm leaning towards something like this or like what I've done in my .
was just released but that changed quite a few things around. instead of using two different binaries it now uses  to decide where the 32/64bit libaries are, but it seems to me that this always expands to 'lib' on NixOS This is what I have so far. Having to ignore collisions is also not really that cool. Well having a running 0.4.1 version would be nice enough, just thought I write about this somewhere
The commit in question:
I marked this as stale due to inactivity. &rarr;
Still important to me.