From f46b2c2ca77368bacbc961d9b5ad82b820b2cff1 Mon Sep 17 00:00:00 2001 From: Anderson Torres Date: Sun, 22 Sep 2024 22:34:57 -0300 Subject: [PATCH] {ftjam,jam}: "remove" They will be split in their own by-name directories. --- .../tools/build-managers/jam/default.nix | 118 ------------------ pkgs/top-level/all-packages.nix | 4 - 2 files changed, 122 deletions(-) delete mode 100644 pkgs/development/tools/build-managers/jam/default.nix diff --git a/pkgs/development/tools/build-managers/jam/default.nix b/pkgs/development/tools/build-managers/jam/default.nix deleted file mode 100644 index bf06954df4de..000000000000 --- a/pkgs/development/tools/build-managers/jam/default.nix +++ /dev/null @@ -1,118 +0,0 @@ -{ lib, stdenv, fetchurl, bison, buildPackages, pkgsBuildTarget }: - -let - mkJam = { pname, version, src, meta ? { } }: stdenv.mkDerivation { - inherit pname version src; - - depsBuildBuild = [ buildPackages.stdenv.cc ]; - nativeBuildInputs = [ bison ]; - - # Jam uses c89 conventions - env.NIX_CFLAGS_COMPILE = lib.optionalString stdenv.cc.isClang "-std=c89"; - - # Jambase expects ar to have flags. - preConfigure = '' - export AR="$AR rc" - ''; - - # When cross-compiling, we need to set the preprocessor macros - # OSMAJOR/OSMINOR/OSPLAT to the values from the target platform, not the - # host platform. This looks a little ridiculous because the vast majority of - # build tools don't embed target-specific information into their binary, but - # in this case we behave more like a compiler than a make(1)-alike. - postPatch = lib.optionalString (stdenv.hostPlatform != stdenv.targetPlatform) '' - cat >>jam.h <