BoomMicrophone/nixpkgs-suyu
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
nixpkgs-suyu/pkgs/tools/system/minijail/tools.nix

41 lines
1.1 KiB
Nix
Raw Permalink Normal View History

pkgs/tools/system: remove dead code
2023-07-25 18:12:44 +02:00
{ lib, buildPythonApplication, pkgsBuildTarget, python, minijail }:
minijail-tools: move constants.json from minijail It makes more sense to keep constants.json in the minijail package, because that's where the tool that consumes it, compile_seccomp_policy, lives. By having it in this package, we can set it as the default location for compile_seccomp_policy, which means it shouldn't ever even need to be specified on the command line (although it still can be). And we can hook into the cross-compilation machinery to get it to automatically use the constants for the right architecture. I've also changed from generating constants.json by running a test program in qemu-user to generating it from LLVM IR, which will save a huge QEMU build dependency.
2022-07-16 15:34:58 +02:00
let
targetClang = pkgsBuildTarget.targetPackages.clangStdenv.cc;
in
minijail-tools: init at 14 This is built from the same source as minijail, but is for all intents and purposes a seperate package. It builds different things, with no overlap, and is under a different license.
2020-03-27 08:11:12 +01:00
buildPythonApplication {
pname = "minijail-tools";
inherit (minijail) version src;
minijail-tools: move constants.json from minijail It makes more sense to keep constants.json in the minijail package, because that's where the tool that consumes it, compile_seccomp_policy, lives. By having it in this package, we can set it as the default location for compile_seccomp_policy, which means it shouldn't ever even need to be specified on the command line (although it still can be). And we can hook into the cross-compilation machinery to get it to automatically use the constants for the right architecture. I've also changed from generating constants.json by running a test program in qemu-user to generating it from LLVM IR, which will save a huge QEMU build dependency.
2022-07-16 15:34:58 +02:00
postPatch = ''
substituteInPlace Makefile --replace /bin/echo echo
'';
postConfigure = ''
substituteInPlace tools/compile_seccomp_policy.py \
--replace "'constants.json'" "'$out/share/constants.json'"
'';
preBuild = ''
make libconstants.gen.c libsyscalls.gen.c
${targetClang}/bin/${targetClang.targetPrefix}cc -S -emit-llvm \
libconstants.gen.c libsyscalls.gen.c
treewide: change pythonForBuild to pythonOnBuildForHost
2023-11-06 02:38:24 +01:00
${python.pythonOnBuildForHost.interpreter} tools/generate_constants_json.py \
minijail-tools: move constants.json from minijail It makes more sense to keep constants.json in the minijail package, because that's where the tool that consumes it, compile_seccomp_policy, lives. By having it in this package, we can set it as the default location for compile_seccomp_policy, which means it shouldn't ever even need to be specified on the command line (although it still can be). And we can hook into the cross-compilation machinery to get it to automatically use the constants for the right architecture. I've also changed from generating constants.json by running a test program in qemu-user to generating it from LLVM IR, which will save a huge QEMU build dependency.
2022-07-16 15:34:58 +02:00
--output constants.json \
libconstants.gen.ll libsyscalls.gen.ll
'';
postInstall = ''
mkdir -p $out/share
cp -v constants.json $out/share/constants.json
'';
minijail-tools: init at 14 This is built from the same source as minijail, but is for all intents and purposes a seperate package. It builds different things, with no overlap, and is under a different license.
2020-03-27 08:11:12 +01:00
meta = with lib; {
homepage = "https://android.googlesource.com/platform/external/minijail/+/refs/heads/master/tools/";
description = "A set of tools for minijail";
license = licenses.asl20;
inherit (minijail.meta) maintainers platforms;
};
}
Reference in a new issue Copy permalink