773233ca77
Intuitively, one cares mainly about the host platform: Platforms differ in meaningful ways but compilation is morally a pure process and probably doesn't care, or those difference are already abstracted away. @Dezgeg also empirically confirmed that > 95% of checks are indeed of the host platform. Yet these attributes in the old cross infrastructure were defined to be the build platform, for expediency. And this was never before changed. (For native builds build and host coincide, so it isn't clear what the intention was.) Fixing this doesn't affect native builds, since again they coincide. It also doesn't affect cross builds of anything in Nixpkgs, as these are no longer used. It could affect external cross builds, but I deem that unlikely as anyone thinking about cross would use more explicit attributes for clarity, all the more so because the rarity of inspecting the build platform.
184 lines
6.9 KiB
Nix
184 lines
6.9 KiB
Nix
/* This file composes a single bootstrapping stage of the Nix Packages
|
|
collection. That is, it imports the functions that build the various
|
|
packages, and calls them with appropriate arguments. The result is a set of
|
|
all the packages in the Nix Packages collection for some particular platform
|
|
for some particular stage.
|
|
|
|
Default arguments are only provided for bootstrapping
|
|
arguments. Normal users should not import this directly but instead
|
|
import `pkgs/default.nix` or `default.nix`. */
|
|
|
|
|
|
{ ## Misc parameters kept the same for all stages
|
|
##
|
|
|
|
# Utility functions, could just import but passing in for efficiency
|
|
lib
|
|
|
|
, # Use to reevaluate Nixpkgs; a dirty hack that should be removed
|
|
nixpkgsFun
|
|
|
|
## Other parameters
|
|
##
|
|
|
|
, # The package set used at build-time. If null, `buildPackages` will
|
|
# be defined internally as the final produced package set itself. This allows
|
|
# us to avoid expensive splicing.
|
|
buildPackages
|
|
|
|
, # The package set used in the next stage. If null, `targetPackages` will be
|
|
# defined internally as the final produced package set itself, just like with
|
|
# `buildPackages` and for the same reasons.
|
|
#
|
|
# THIS IS A HACK for compilers that don't think critically about cross-
|
|
# compilation. Please do *not* use unless you really know what you are doing.
|
|
targetPackages
|
|
|
|
, # The standard environment to use for building packages.
|
|
stdenv
|
|
|
|
, # This is used because stdenv replacement and the stdenvCross do benefit from
|
|
# the overridden configuration provided by the user, as opposed to the normal
|
|
# bootstrapping stdenvs.
|
|
allowCustomOverrides
|
|
|
|
, # Non-GNU/Linux OSes are currently "impure" platforms, with their libc
|
|
# outside of the store. Thus, GCC, GFortran, & co. must always look for files
|
|
# in standard system directories (/usr/include, etc.)
|
|
noSysDirs ? stdenv.buildPlatform.system != "x86_64-freebsd"
|
|
&& stdenv.buildPlatform.system != "i686-freebsd"
|
|
&& stdenv.buildPlatform.system != "x86_64-solaris"
|
|
&& stdenv.buildPlatform.system != "x86_64-kfreebsd-gnu"
|
|
|
|
, # The configuration attribute set
|
|
config
|
|
|
|
, # A list of overlays (Additional `self: super: { .. }` customization
|
|
# functions) to be fixed together in the produced package set
|
|
overlays
|
|
}:
|
|
|
|
let
|
|
stdenvAdapters = self: super:
|
|
let res = import ../stdenv/adapters.nix self; in res // {
|
|
stdenvAdapters = res;
|
|
};
|
|
|
|
trivialBuilders = self: super:
|
|
import ../build-support/trivial-builders.nix {
|
|
inherit lib; inherit (self) stdenv stdenvNoCC; inherit (self.xorg) lndir;
|
|
};
|
|
|
|
stdenvBootstappingAndPlatforms = self: super: {
|
|
buildPackages = (if buildPackages == null then self else buildPackages)
|
|
// { recurseForDerivations = false; };
|
|
targetPackages = (if targetPackages == null then self else targetPackages)
|
|
// { recurseForDerivations = false; };
|
|
inherit stdenv;
|
|
};
|
|
|
|
# The old identifiers for cross-compiling. These should eventually be removed,
|
|
# and the packages that rely on them refactored accordingly.
|
|
platformCompat = self: super: {
|
|
buildPlatform = lib.warn
|
|
"top-level `buildPlatform` is deprecated since 18.09. Please use `stdenv.buildPlatform`."
|
|
super.stdenv.buildPlatform;
|
|
hostPlatform = lib.warn
|
|
"top-level `hostPlatform` is deprecated since 18.09. Please use `stdenv.hostPlatform`."
|
|
super.stdenv.hostPlatform;
|
|
targetPlatform = lib.warn
|
|
"top-level `targetPlatform` is deprecated since 18.09. Please use `stdenv.targetPlatform`."
|
|
super.stdenv.targetPlatform;
|
|
inherit (super.stdenv.hostPlatform) system;
|
|
};
|
|
|
|
splice = self: super: import ./splice.nix lib self (buildPackages != null);
|
|
|
|
allPackages = self: super:
|
|
let res = import ./all-packages.nix
|
|
{ inherit lib noSysDirs config; }
|
|
res self;
|
|
in res;
|
|
|
|
aliases = self: super: lib.optionalAttrs (config.allowAliases or true) (import ./aliases.nix lib self super);
|
|
|
|
# stdenvOverrides is used to avoid having multiple of versions
|
|
# of certain dependencies that were used in bootstrapping the
|
|
# standard environment.
|
|
stdenvOverrides = self: super:
|
|
(super.stdenv.overrides or (_: _: {})) self super;
|
|
|
|
# Allow packages to be overridden globally via the `packageOverrides'
|
|
# configuration option, which must be a function that takes `pkgs'
|
|
# as an argument and returns a set of new or overridden packages.
|
|
# The `packageOverrides' function is called with the *original*
|
|
# (un-overridden) set of packages, allowing packageOverrides
|
|
# attributes to refer to the original attributes (e.g. "foo =
|
|
# ... pkgs.foo ...").
|
|
configOverrides = self: super:
|
|
lib.optionalAttrs allowCustomOverrides
|
|
((config.packageOverrides or (super: {})) super);
|
|
|
|
# Convenience attributes for instantitating package sets. Each of
|
|
# these will instantiate a new version of allPackages. Currently the
|
|
# following package sets are provided:
|
|
#
|
|
# - pkgsCross.<system> where system is a member of lib.systems.examples
|
|
# - pkgsMusl
|
|
# - pkgsi686Linux
|
|
otherPackageSets = self: super: {
|
|
# This maps each entry in lib.systems.examples to its own package
|
|
# set. Each of these will contain all packages cross compiled for
|
|
# that target system. For instance, pkgsCross.rasberryPi.hello,
|
|
# will refer to the "hello" package built for the ARM6-based
|
|
# Raspberry Pi.
|
|
pkgsCross = lib.mapAttrs (n: crossSystem:
|
|
nixpkgsFun { inherit crossSystem; })
|
|
lib.systems.examples;
|
|
|
|
# All packages built with the Musl libc. This will override the
|
|
# default GNU libc on Linux systems. Non-Linux systems are not
|
|
# supported.
|
|
pkgsMusl = if stdenv.hostPlatform.isLinux then nixpkgsFun {
|
|
localSystem = {
|
|
parsed = stdenv.hostPlatform.parsed // {
|
|
abi = {
|
|
"gnu" = lib.systems.parse.abis.musl;
|
|
"gnueabi" = lib.systems.parse.abis.musleabi;
|
|
"gnueabihf" = lib.systems.parse.abis.musleabihf;
|
|
}.${stdenv.hostPlatform.parsed.abi.name} or lib.systems.parse.abis.musl;
|
|
};
|
|
};
|
|
} else throw "Musl libc only supports Linux systems.";
|
|
|
|
# All packages built for i686 Linux.
|
|
# Used by wine, firefox with debugging version of Flash, ...
|
|
pkgsi686Linux = assert stdenv.hostPlatform.isLinux; nixpkgsFun {
|
|
localSystem = {
|
|
parsed = stdenv.hostPlatform.parsed // {
|
|
cpu = lib.systems.parse.cpuTypes.i686;
|
|
};
|
|
};
|
|
};
|
|
};
|
|
|
|
# The complete chain of package set builders, applied from top to bottom.
|
|
# stdenvOverlays must be last as it brings package forward from the
|
|
# previous bootstrapping phases which have already been overlayed.
|
|
toFix = lib.foldl' (lib.flip lib.extends) (self: {}) ([
|
|
stdenvBootstappingAndPlatforms
|
|
platformCompat
|
|
stdenvAdapters
|
|
trivialBuilders
|
|
splice
|
|
allPackages
|
|
otherPackageSets
|
|
aliases
|
|
configOverrides
|
|
] ++ overlays ++ [
|
|
stdenvOverrides ]);
|
|
|
|
in
|
|
# Return the complete set of packages.
|
|
lib.fix toFix
|