about summary refs log tree commit diff
path: root/pkgs/games/build-support/default.nix
diff options
context:
space:
mode:
authoraszlig <aszlig@nix.build>2018-07-31 16:47:44 +0200
committeraszlig <aszlig@nix.build>2018-07-31 16:47:44 +0200
commit0b0b5d75016bcdf7c6f7c540ef80a15e7542d2b5 (patch)
tree1d9fdc80f3d3127bcbf5bcaffc39609561bb1410 /pkgs/games/build-support/default.nix
parenta8e406920bb11a2c53558d1398b3a66efd267e60 (diff)
games: Move FMOD fixing from Bastion to setup hook
Thanks to @layus for pointing out that there is at least one other game
(Epistory) which has the same FMOD issue as Bastion has.

So I decided to move this into a setup hook that automatically discovers
whether it's the affected FMOD version and NOPs out the calls to
system().

In summary: If another game is affected, all that's needed now is to add
fixFmodHook to nativeBuildInputs.

Signed-off-by: aszlig <aszlig@nix.build>
Cc: @layus
Diffstat (limited to 'pkgs/games/build-support/default.nix')
-rw-r--r--pkgs/games/build-support/default.nix2
1 files changed, 1 insertions, 1 deletions
diff --git a/pkgs/games/build-support/default.nix b/pkgs/games/build-support/default.nix
index 0e7574ec..ac152659 100644
--- a/pkgs/games/build-support/default.nix
+++ b/pkgs/games/build-support/default.nix
@@ -7,5 +7,5 @@
   buildUnity = callPackage ./build-unity.nix {};
   monogamePatcher = callPackage ./monogame-patcher {};
 
-  inherit (callPackages ./setup-hooks {}) gogUnpackHook;
+  inherit (callPackages ./setup-hooks {}) fixFmodHook gogUnpackHook;
 }