dadc7eb329
Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well.
40 lines
1.1 KiB
Nix
40 lines
1.1 KiB
Nix
{ stdenv, pkgs, cores, runtimeShell }:
|
|
|
|
assert cores != [];
|
|
|
|
with pkgs.lib;
|
|
|
|
let
|
|
|
|
script = exec: ''
|
|
#!${runtimeShell}
|
|
nohup sh -c "pkill -SIGTSTP kodi" &
|
|
# https://forum.kodi.tv/showthread.php?tid=185074&pid=1622750#pid1622750
|
|
nohup sh -c "sleep 10 && ${exec} '$@' -f;pkill -SIGCONT kodi"
|
|
'';
|
|
scriptSh = exec: pkgs.writeScript ("kodi-"+exec.name) (script exec.path);
|
|
execs = map (core: rec { name = core.core; path = core+"/bin/retroarch-"+name;}) cores;
|
|
|
|
in
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "kodi-retroarch-advanced-launchers-${version}";
|
|
version = "0.2";
|
|
|
|
dontBuild = true;
|
|
|
|
buildCommand = ''
|
|
mkdir -p $out/bin
|
|
${stdenv.lib.concatMapStrings (exec: "ln -s ${scriptSh exec} $out/bin/kodi-${exec.name};") execs}
|
|
'';
|
|
|
|
meta = {
|
|
description = "Kodi retroarch advanced launchers";
|
|
longDescription = ''
|
|
These retroarch launchers are intended to be used with
|
|
advanced (emulation) launcher for Kodi since device input is
|
|
otherwise caught by both Kodi and the retroarch process.
|
|
'';
|
|
license = stdenv.lib.licenses.gpl3;
|
|
};
|
|
}
|