2009-02-10 16:48:30 +01:00
|
|
|
/* This file contains various functions that take a stdenv and return
|
|
|
|
a new stdenv with different behaviour, e.g. using a different C
|
|
|
|
compiler. */
|
|
|
|
|
2014-02-04 16:58:12 +01:00
|
|
|
pkgs:
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-02-10 16:48:30 +01:00
|
|
|
rec {
|
|
|
|
|
|
|
|
|
|
|
|
# Override the compiler in stdenv for specific packages.
|
2015-01-09 20:22:12 +01:00
|
|
|
overrideCC = stdenv: cc: stdenv.override { allowedRequisites = null; cc = cc; };
|
2009-02-10 16:48:30 +01:00
|
|
|
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-02-10 16:48:30 +01:00
|
|
|
# Add some arbitrary packages to buildInputs for specific packages.
|
2010-08-06 22:23:35 +02:00
|
|
|
# Used to override packages in stdenv like Make. Should not be used
|
2009-02-10 16:48:30 +01:00
|
|
|
# for other dependencies.
|
2014-02-04 17:18:38 +01:00
|
|
|
overrideInStdenv = stdenv: pkgs:
|
2014-10-06 22:11:05 +02:00
|
|
|
stdenv.override (prev: { allowedRequisites = null; extraBuildInputs = prev.extraBuildInputs or [] ++ pkgs; });
|
2009-02-10 16:48:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
# Override the setup script of stdenv. Useful for testing new
|
|
|
|
# versions of the setup script without causing a rebuild of
|
|
|
|
# everything.
|
|
|
|
#
|
|
|
|
# Example:
|
|
|
|
# randomPkg = import ../bla { ...
|
|
|
|
# stdenv = overrideSetup stdenv ../stdenv/generic/setup-latest.sh;
|
|
|
|
# };
|
2014-02-04 17:18:38 +01:00
|
|
|
overrideSetup = stdenv: setupScript: stdenv.override { inherit setupScript; };
|
2009-02-10 16:48:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
# Return a modified stdenv that tries to build statically linked
|
|
|
|
# binaries.
|
|
|
|
makeStaticBinaries = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
NIX_CFLAGS_LINK = "-static";
|
|
|
|
configureFlags =
|
2012-12-28 19:35:35 +01:00
|
|
|
toString args.configureFlags or ""
|
2009-02-10 16:48:30 +01:00
|
|
|
+ " --disable-shared"; # brrr...
|
|
|
|
});
|
|
|
|
isStatic = true;
|
2014-02-04 16:58:12 +01:00
|
|
|
};
|
2009-02-10 16:48:30 +01:00
|
|
|
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2011-12-14 15:31:56 +01:00
|
|
|
# Return a modified stdenv that builds static libraries instead of
|
|
|
|
# shared libraries.
|
|
|
|
makeStaticLibraries = stdenv: stdenv //
|
2010-01-21 22:42:17 +01:00
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
dontDisableStatic = true;
|
|
|
|
configureFlags =
|
2012-12-28 19:35:35 +01:00
|
|
|
toString args.configureFlags or ""
|
2011-12-14 15:31:56 +01:00
|
|
|
+ " --enable-static --disable-shared";
|
2010-01-21 22:42:17 +01:00
|
|
|
});
|
2014-02-04 16:58:12 +01:00
|
|
|
};
|
2010-01-21 22:42:17 +01:00
|
|
|
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-11-17 22:14:57 +01:00
|
|
|
# Return a modified stdenv that adds a cross compiler to the
|
|
|
|
# builds.
|
I made the whole nixpkgs dependencies available to the cross compiler, no
needing to keep a new tree of expressions apart for the expressions to get
cross-compiled.
I changed the whole way of using cross compilation with nixpkgs, which before
was done through a simple adapter.
Now the adapter became complex, and I've tried to avoid the most obvious
recursivities. For example, the fetchurl expression should
never be cross-compiled, as the gmp, mpfr, and some others, like
some ncurses, perl, ... I made overrided copies of those necessary as
perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that
the stdenv (capable of cross compilation) is built upon stdenvNoCross using
an adapter.
So, to cross compile, instead of building using "nixpkgs/default.nix",
you should build with your
own "myarchiteture.nix", which should have contents like these, for example:
import /etc/nixos/nixpkgs/default.nix
{
crossSystem = {
config = "armv5tel-unknown-linux-gnueabi";
bigEndian = false;
arch = "arm";
float = "soft";
};
}
svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
|
|
|
makeStdenvCross = stdenv: cross: binutilsCross: gccCross: stdenv //
|
2012-12-28 19:20:09 +01:00
|
|
|
{ mkDerivation = {name ? "", buildInputs ? [], nativeBuildInputs ? [],
|
|
|
|
propagatedBuildInputs ? [], propagatedNativeBuildInputs ? [],
|
|
|
|
selfNativeBuildInput ? false, ...}@args: let
|
Attention, people who care on the builders for native builds. In the stdenv
derivation, the "buildInputs" in every stdenv mkDerivation don't map now
directly to the environment
variable "buildInputs" in the builder, but "buildNativeInputs". So, the inputs
build by the native compiler.
When cross compiling, they will map to the environment variable "buildInputs"
(yes, now the same name), which means does to be built with the cross compiler.
I think I improved the naming of variables a bit. There was a big mess,
specially in the stdenv adapter for cross building, and also in the default
builder script.
I also tried to add proper manager of propagatedInputBuilds, these being
propagated considering the host or build origin of that input build (so, at the
end, being those propagatedInputBuilds being propagated properly to the native
or the cross compiler.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18477
2009-11-20 00:05:11 +01:00
|
|
|
|
|
|
|
# *BuildInputs exists temporarily as another name for
|
|
|
|
# *HostInputs.
|
|
|
|
|
2010-03-04 15:44:38 +01:00
|
|
|
# In nixpkgs, sometimes 'null' gets in as a buildInputs element,
|
|
|
|
# and we handle that through isAttrs.
|
top-level: Introduce `buildPackages` for resolving build-time deps
[N.B., this package also applies to the commits that follow it in the same
PR.]
In most cases, buildPackages = pkgs so things work just as before. For
cross compiling, however, buildPackages is resolved as the previous
bootstrapping stage. This allows us to avoid the mkDerivation hacks cross
compiling currently uses today.
To avoid a massive refactor, callPackage will splice together both package
sets. Again to avoid churn, it uses the old `nativeDrv` vs `crossDrv` to do
so. So now, whether cross compiling or not, packages with get a `nativeDrv`
and `crossDrv`---in the non-cross-compiling case they are simply the same
derivation. This is good because it reduces the divergence between the
cross and non-cross dataflow. See `pkgs/top-level/splice.nix` for a comment
along the lines of the preceding paragraph, and the code that does this
splicing.
Also, `forceNativeDrv` is replaced with `forceNativePackages`. The latter
resolves `pkgs` unless the host platform is different from the build
platform, in which case it resolves to `buildPackages`. Note that the
target platform is not important here---it will not prevent
`forcedNativePackages` from resolving to `pkgs`.
--------
Temporarily, we make preserve some dubious decisions in the name of preserving
hashes:
Most importantly, we don't distinguish between "host" and "target" in the
autoconf sense. This leads to the proliferation of *Cross derivations
currently used. What we ought to is resolve native deps of the cross "build
packages" (build = host != target) package set against the "vanilla
packages" (build = host = target) package set. Instead, "build packages"
uses itself, with (informally) target != build in all cases.
This is wrong because it violates the "sliding window" principle of
bootstrapping stages that shifting the platform triple of one stage to the
left coincides with the next stage's platform triple. Only because we don't
explicitly distinguish between "host" and "target" does it appear that the
"sliding window" principle is preserved--indeed it is over the reductionary
"platform double" of just "build" and "host/target".
Additionally, we build libc, libgcc, etc in the same stage as the compilers
themselves, which is wrong because they are used at runtime, not build
time. Fixing this is somewhat subtle, and the solution and problem will be
better explained in the commit that does fix it.
Commits after this will solve both these issues, at the expense of breaking
cross hashes. Native hashes won't be broken, thankfully.
--------
Did the temporary ugliness pan out? Of the packages that currently build in
`release-cross.nix`, the only ones that have their hash changed are
`*.gcc.crossDrv` and `bootstrapTools.*.coreutilsMinimal`. In both cases I
think it doesn't matter.
1. GCC when doing a `build = host = target = foreign` build (maximally
cross), still defines environment variables like `CPATH`[1] with
packages. This seems assuredly wrong because whether gcc dynamically
links those, or the programs built by gcc dynamically link those---I
have no idea which case is reality---they should be foreign. Therefore,
in all likelihood, I just made the gcc less broken.
2. Coreutils (ab)used the old cross-compiling infrastructure to depend on
a native version of itself. When coreutils was overwritten to be built
with fewer features, the native version it used would also be
overwritten because the binding was tight. Now it uses the much looser
`BuildPackages.coreutils` which is just fine as a richer build dep
doesn't cause any problems and avoids a rebuild.
So, in conclusion I'd say the conservatism payed off. Onward to actually
raking the muck in the next PR!
[1]: https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html
2016-12-18 08:51:18 +01:00
|
|
|
nativeBuildInputsDrvs = nativeBuildInputs;
|
|
|
|
buildInputsDrvs = buildInputs;
|
|
|
|
propagatedBuildInputsDrvs = propagatedBuildInputs;
|
|
|
|
propagatedNativeBuildInputsDrvs = propagatedNativeBuildInputs;
|
Attention, people who care on the builders for native builds. In the stdenv
derivation, the "buildInputs" in every stdenv mkDerivation don't map now
directly to the environment
variable "buildInputs" in the builder, but "buildNativeInputs". So, the inputs
build by the native compiler.
When cross compiling, they will map to the environment variable "buildInputs"
(yes, now the same name), which means does to be built with the cross compiler.
I think I improved the naming of variables a bit. There was a big mess,
specially in the stdenv adapter for cross building, and also in the default
builder script.
I also tried to add proper manager of propagatedInputBuilds, these being
propagated considering the host or build origin of that input build (so, at the
end, being those propagatedInputBuilds being propagated properly to the native
or the cross compiler.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18477
2009-11-20 00:05:11 +01:00
|
|
|
|
2012-12-28 19:20:09 +01:00
|
|
|
# The base stdenv already knows that nativeBuildInputs and
|
Attention, people who care on the builders for native builds. In the stdenv
derivation, the "buildInputs" in every stdenv mkDerivation don't map now
directly to the environment
variable "buildInputs" in the builder, but "buildNativeInputs". So, the inputs
build by the native compiler.
When cross compiling, they will map to the environment variable "buildInputs"
(yes, now the same name), which means does to be built with the cross compiler.
I think I improved the naming of variables a bit. There was a big mess,
specially in the stdenv adapter for cross building, and also in the default
builder script.
I also tried to add proper manager of propagatedInputBuilds, these being
propagated considering the host or build origin of that input build (so, at the
end, being those propagatedInputBuilds being propagated properly to the native
or the cross compiler.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18477
2009-11-20 00:05:11 +01:00
|
|
|
# buildInputs should be built with the usual gcc-wrapper
|
|
|
|
# And the same for propagatedBuildInputs.
|
2012-12-28 19:08:19 +01:00
|
|
|
nativeDrv = stdenv.mkDerivation args;
|
Attention, people who care on the builders for native builds. In the stdenv
derivation, the "buildInputs" in every stdenv mkDerivation don't map now
directly to the environment
variable "buildInputs" in the builder, but "buildNativeInputs". So, the inputs
build by the native compiler.
When cross compiling, they will map to the environment variable "buildInputs"
(yes, now the same name), which means does to be built with the cross compiler.
I think I improved the naming of variables a bit. There was a big mess,
specially in the stdenv adapter for cross building, and also in the default
builder script.
I also tried to add proper manager of propagatedInputBuilds, these being
propagated considering the host or build origin of that input build (so, at the
end, being those propagatedInputBuilds being propagated properly to the native
or the cross compiler.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18477
2009-11-20 00:05:11 +01:00
|
|
|
|
Big fixes in the cross build:
- Before this changes, cflags and ldflags for the native and the cross compiler
got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are
independant now, but enough, I think.
- Fixed the generic stdenv expression, which did a big mess on buildInputs and
buildNativeInputs. Now it distinguishes when there is a stdenvCross or not.
Maybe we should have a single stdenv and forget about the stdenvCross
adapter - this could end in a stdenv a bit complex, but simpler than the
generic stdenv + adapter.
- Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH
now works for both the cross and the native compilers, but I think this
should work well for most cases I can think of.
- I tried to fix the guile expression to cross-biuld; guile is built, but not
its manual, so the derivation still fails. Guile requires patching to
cross-build, as far as I understnad.
- Made the glibcCross build to be done through the usage of a
gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it
directly.
- Trying to make physfs (a neverball dependency) cross build.
- Updated the gcc expression to support building a cross compiler without getting
derivation variables mixed with those of the stdenvCross.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
|
|
|
# Temporary expression until the cross_renaming, to handle the
|
|
|
|
# case of pkgconfig given as buildInput, but to be used as
|
2012-12-28 19:20:09 +01:00
|
|
|
# nativeBuildInput.
|
2012-12-28 19:42:10 +01:00
|
|
|
hostAsNativeDrv = drv:
|
2012-12-28 19:37:42 +01:00
|
|
|
builtins.unsafeDiscardStringContext drv.nativeDrv.drvPath
|
|
|
|
== builtins.unsafeDiscardStringContext drv.crossDrv.drvPath;
|
2010-03-04 15:44:38 +01:00
|
|
|
buildInputsNotNull = stdenv.lib.filter
|
2012-12-28 19:08:19 +01:00
|
|
|
(drv: builtins.isAttrs drv && drv ? nativeDrv) buildInputs;
|
2012-12-28 19:42:10 +01:00
|
|
|
nativeInputsFromBuildInputs = stdenv.lib.filter hostAsNativeDrv buildInputsNotNull;
|
Big fixes in the cross build:
- Before this changes, cflags and ldflags for the native and the cross compiler
got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are
independant now, but enough, I think.
- Fixed the generic stdenv expression, which did a big mess on buildInputs and
buildNativeInputs. Now it distinguishes when there is a stdenvCross or not.
Maybe we should have a single stdenv and forget about the stdenvCross
adapter - this could end in a stdenv a bit complex, but simpler than the
generic stdenv + adapter.
- Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH
now works for both the cross and the native compilers, but I think this
should work well for most cases I can think of.
- I tried to fix the guile expression to cross-biuld; guile is built, but not
its manual, so the derivation still fails. Guile requires patching to
cross-build, as far as I understnad.
- Made the glibcCross build to be done through the usage of a
gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it
directly.
- Trying to make physfs (a neverball dependency) cross build.
- Updated the gcc expression to support building a cross compiler without getting
derivation variables mixed with those of the stdenvCross.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
|
|
|
|
top-level: Introduce `buildPackages` for resolving build-time deps
[N.B., this package also applies to the commits that follow it in the same
PR.]
In most cases, buildPackages = pkgs so things work just as before. For
cross compiling, however, buildPackages is resolved as the previous
bootstrapping stage. This allows us to avoid the mkDerivation hacks cross
compiling currently uses today.
To avoid a massive refactor, callPackage will splice together both package
sets. Again to avoid churn, it uses the old `nativeDrv` vs `crossDrv` to do
so. So now, whether cross compiling or not, packages with get a `nativeDrv`
and `crossDrv`---in the non-cross-compiling case they are simply the same
derivation. This is good because it reduces the divergence between the
cross and non-cross dataflow. See `pkgs/top-level/splice.nix` for a comment
along the lines of the preceding paragraph, and the code that does this
splicing.
Also, `forceNativeDrv` is replaced with `forceNativePackages`. The latter
resolves `pkgs` unless the host platform is different from the build
platform, in which case it resolves to `buildPackages`. Note that the
target platform is not important here---it will not prevent
`forcedNativePackages` from resolving to `pkgs`.
--------
Temporarily, we make preserve some dubious decisions in the name of preserving
hashes:
Most importantly, we don't distinguish between "host" and "target" in the
autoconf sense. This leads to the proliferation of *Cross derivations
currently used. What we ought to is resolve native deps of the cross "build
packages" (build = host != target) package set against the "vanilla
packages" (build = host = target) package set. Instead, "build packages"
uses itself, with (informally) target != build in all cases.
This is wrong because it violates the "sliding window" principle of
bootstrapping stages that shifting the platform triple of one stage to the
left coincides with the next stage's platform triple. Only because we don't
explicitly distinguish between "host" and "target" does it appear that the
"sliding window" principle is preserved--indeed it is over the reductionary
"platform double" of just "build" and "host/target".
Additionally, we build libc, libgcc, etc in the same stage as the compilers
themselves, which is wrong because they are used at runtime, not build
time. Fixing this is somewhat subtle, and the solution and problem will be
better explained in the commit that does fix it.
Commits after this will solve both these issues, at the expense of breaking
cross hashes. Native hashes won't be broken, thankfully.
--------
Did the temporary ugliness pan out? Of the packages that currently build in
`release-cross.nix`, the only ones that have their hash changed are
`*.gcc.crossDrv` and `bootstrapTools.*.coreutilsMinimal`. In both cases I
think it doesn't matter.
1. GCC when doing a `build = host = target = foreign` build (maximally
cross), still defines environment variables like `CPATH`[1] with
packages. This seems assuredly wrong because whether gcc dynamically
links those, or the programs built by gcc dynamically link those---I
have no idea which case is reality---they should be foreign. Therefore,
in all likelihood, I just made the gcc less broken.
2. Coreutils (ab)used the old cross-compiling infrastructure to depend on
a native version of itself. When coreutils was overwritten to be built
with fewer features, the native version it used would also be
overwritten because the binding was tight. Now it uses the much looser
`BuildPackages.coreutils` which is just fine as a richer build dep
doesn't cause any problems and avoids a rebuild.
So, in conclusion I'd say the conservatism payed off. Onward to actually
raking the muck in the next PR!
[1]: https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html
2016-12-18 08:51:18 +01:00
|
|
|
in stdenv.mkDerivation (args // {
|
I made the whole nixpkgs dependencies available to the cross compiler, no
needing to keep a new tree of expressions apart for the expressions to get
cross-compiled.
I changed the whole way of using cross compilation with nixpkgs, which before
was done through a simple adapter.
Now the adapter became complex, and I've tried to avoid the most obvious
recursivities. For example, the fetchurl expression should
never be cross-compiled, as the gmp, mpfr, and some others, like
some ncurses, perl, ... I made overrided copies of those necessary as
perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that
the stdenv (capable of cross compilation) is built upon stdenvNoCross using
an adapter.
So, to cross compile, instead of building using "nixpkgs/default.nix",
you should build with your
own "myarchiteture.nix", which should have contents like these, for example:
import /etc/nixos/nixpkgs/default.nix
{
crossSystem = {
config = "armv5tel-unknown-linux-gnueabi";
bigEndian = false;
arch = "arm";
float = "soft";
};
}
svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
|
|
|
name = name + "-" + cross.config;
|
2012-12-28 19:20:09 +01:00
|
|
|
nativeBuildInputs = nativeBuildInputsDrvs
|
Big fixes in the cross build:
- Before this changes, cflags and ldflags for the native and the cross compiler
got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are
independant now, but enough, I think.
- Fixed the generic stdenv expression, which did a big mess on buildInputs and
buildNativeInputs. Now it distinguishes when there is a stdenvCross or not.
Maybe we should have a single stdenv and forget about the stdenvCross
adapter - this could end in a stdenv a bit complex, but simpler than the
generic stdenv + adapter.
- Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH
now works for both the cross and the native compilers, but I think this
should work well for most cases I can think of.
- I tried to fix the guile expression to cross-biuld; guile is built, but not
its manual, so the derivation still fails. Guile requires patching to
cross-build, as far as I understnad.
- Made the glibcCross build to be done through the usage of a
gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it
directly.
- Trying to make physfs (a neverball dependency) cross build.
- Updated the gcc expression to support building a cross compiler without getting
derivation variables mixed with those of the stdenvCross.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
|
|
|
++ nativeInputsFromBuildInputs
|
2016-04-14 08:59:47 +02:00
|
|
|
++ [ gccCross binutilsCross ]
|
|
|
|
++ stdenv.lib.optional selfNativeBuildInput nativeDrv
|
|
|
|
# without proper `file` command, libtool sometimes fails
|
|
|
|
# to recognize 64-bit DLLs
|
|
|
|
++ stdenv.lib.optional (cross.config == "x86_64-w64-mingw32") pkgs.file
|
|
|
|
;
|
2009-11-24 00:16:40 +01:00
|
|
|
|
|
|
|
# Cross-linking dynamic libraries, every buildInput should
|
|
|
|
# be propagated because ld needs the -rpath-link to find
|
|
|
|
# any library needed to link the program dynamically at
|
|
|
|
# loader time. ld(1) explains it.
|
|
|
|
buildInputs = [];
|
2012-12-28 19:37:42 +01:00
|
|
|
propagatedBuildInputs = propagatedBuildInputsDrvs ++ buildInputsDrvs;
|
2012-12-28 19:20:09 +01:00
|
|
|
propagatedNativeBuildInputs = propagatedNativeBuildInputsDrvs;
|
I made the whole nixpkgs dependencies available to the cross compiler, no
needing to keep a new tree of expressions apart for the expressions to get
cross-compiled.
I changed the whole way of using cross compilation with nixpkgs, which before
was done through a simple adapter.
Now the adapter became complex, and I've tried to avoid the most obvious
recursivities. For example, the fetchurl expression should
never be cross-compiled, as the gmp, mpfr, and some others, like
some ncurses, perl, ... I made overrided copies of those necessary as
perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that
the stdenv (capable of cross compilation) is built upon stdenvNoCross using
an adapter.
So, to cross compile, instead of building using "nixpkgs/default.nix",
you should build with your
own "myarchiteture.nix", which should have contents like these, for example:
import /etc/nixos/nixpkgs/default.nix
{
crossSystem = {
config = "armv5tel-unknown-linux-gnueabi";
bigEndian = false;
arch = "arm";
float = "soft";
};
}
svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
|
|
|
|
|
|
|
crossConfig = cross.config;
|
2012-12-28 19:35:35 +01:00
|
|
|
} // args.crossAttrs or {});
|
2010-03-06 22:41:01 +01:00
|
|
|
} // {
|
2016-12-24 19:55:11 +01:00
|
|
|
inherit gccCross binutilsCross;
|
2015-01-25 01:45:31 +01:00
|
|
|
ccCross = gccCross;
|
2010-03-06 22:41:01 +01:00
|
|
|
};
|
2009-03-30 15:22:19 +02:00
|
|
|
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-03-30 15:22:19 +02:00
|
|
|
/* Modify a stdenv so that the specified attributes are added to
|
|
|
|
every derivation returned by its mkDerivation function.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
stdenvNoOptimise =
|
|
|
|
addAttrsToDerivation
|
|
|
|
{ NIX_CFLAGS_COMPILE = "-O0"; }
|
|
|
|
stdenv;
|
|
|
|
*/
|
|
|
|
addAttrsToDerivation = extraAttrs: stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // extraAttrs); };
|
|
|
|
|
|
|
|
|
2009-08-28 18:45:56 +02:00
|
|
|
/* Return a modified stdenv that builds packages with GCC's coverage
|
|
|
|
instrumentation. The coverage note files (*.gcno) are stored in
|
2009-09-01 23:56:46 +02:00
|
|
|
$out/.build, along with the source code of the package, to enable
|
|
|
|
programs like lcov to produce pretty-printed reports.
|
2009-08-28 18:45:56 +02:00
|
|
|
*/
|
|
|
|
addCoverageInstrumentation = stdenv:
|
2014-03-03 13:39:30 +01:00
|
|
|
overrideInStdenv stdenv [ pkgs.enableGCOVInstrumentation pkgs.keepBuildTree ];
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-11-16 23:23:11 +01:00
|
|
|
|
|
|
|
/* Replace the meta.maintainers field of a derivation. This is useful
|
|
|
|
when you want to fork to update some packages without disturbing other
|
|
|
|
developers.
|
|
|
|
|
|
|
|
e.g.: in all-packages.nix:
|
|
|
|
|
|
|
|
# remove all maintainers.
|
|
|
|
defaultStdenv = replaceMaintainersField allStdenvs.stdenv pkgs [];
|
|
|
|
*/
|
|
|
|
replaceMaintainersField = stdenv: pkgs: maintainers: stdenv //
|
|
|
|
{ mkDerivation = args:
|
2014-02-04 16:58:12 +01:00
|
|
|
stdenv.lib.recursiveUpdate
|
2009-11-16 23:23:11 +01:00
|
|
|
(stdenv.mkDerivation args)
|
|
|
|
{ meta.maintainers = maintainers; };
|
|
|
|
};
|
2009-11-21 18:50:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
/* Use the trace output to report all processed derivations with their
|
|
|
|
license name.
|
|
|
|
*/
|
|
|
|
traceDrvLicenses = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args:
|
|
|
|
let
|
|
|
|
pkg = stdenv.mkDerivation args;
|
|
|
|
printDrvPath = val: let
|
|
|
|
drvPath = builtins.unsafeDiscardStringContext pkg.drvPath;
|
2012-12-28 19:35:35 +01:00
|
|
|
license = pkg.meta.license or null;
|
2009-11-21 18:50:00 +01:00
|
|
|
in
|
2012-12-28 19:35:35 +01:00
|
|
|
builtins.trace "@:drv:${toString drvPath}:${builtins.toString license}:@" val;
|
2009-11-21 18:50:00 +01:00
|
|
|
in pkg // {
|
|
|
|
outPath = printDrvPath pkg.outPath;
|
|
|
|
drvPath = printDrvPath pkg.drvPath;
|
|
|
|
};
|
|
|
|
};
|
2009-11-22 18:04:33 +01:00
|
|
|
|
2012-10-31 13:41:54 +01:00
|
|
|
|
2009-11-22 18:04:33 +01:00
|
|
|
/* Abort if the license predicate is not verified for a derivation
|
|
|
|
declared with mkDerivation.
|
|
|
|
|
|
|
|
One possible predicate to avoid all non-free packages can be achieved
|
|
|
|
with the following function:
|
|
|
|
|
|
|
|
isFree = license: with builtins;
|
|
|
|
if isNull license then true
|
|
|
|
else if isList license then lib.all isFree license
|
|
|
|
else license != "non-free" && license != "unfree";
|
|
|
|
|
|
|
|
This adapter can be defined on the defaultStdenv definition. You can
|
|
|
|
use it by patching the all-packages.nix file or by using the override
|
|
|
|
feature of ~/.nixpkgs/config.nix .
|
|
|
|
*/
|
|
|
|
validateLicenses = licensePred: stdenv: stdenv //
|
|
|
|
{ mkDerivation = args:
|
|
|
|
let
|
|
|
|
pkg = stdenv.mkDerivation args;
|
2011-11-20 21:53:15 +01:00
|
|
|
drv = builtins.unsafeDiscardStringContext pkg.drvPath;
|
2009-11-22 18:04:33 +01:00
|
|
|
license =
|
2012-12-28 19:35:35 +01:00
|
|
|
pkg.meta.license or
|
2011-11-20 21:53:15 +01:00
|
|
|
# Fixed-output derivations such as source tarballs usually
|
|
|
|
# don't have licensing information, but that's OK.
|
2012-12-28 19:35:35 +01:00
|
|
|
(pkg.outputHash or
|
|
|
|
(builtins.trace
|
|
|
|
"warning: ${drv} lacks licensing information" null));
|
2009-11-22 18:04:33 +01:00
|
|
|
|
|
|
|
validate = arg:
|
|
|
|
if licensePred license then arg
|
2011-11-20 21:42:05 +01:00
|
|
|
else abort ''
|
2011-11-20 21:53:15 +01:00
|
|
|
while building ${drv}:
|
2011-11-20 21:42:05 +01:00
|
|
|
license `${builtins.toString license}' does not pass the predicate.
|
|
|
|
'';
|
2009-11-22 18:04:33 +01:00
|
|
|
|
|
|
|
in pkg // {
|
|
|
|
outPath = validate pkg.outPath;
|
|
|
|
drvPath = validate pkg.drvPath;
|
|
|
|
};
|
|
|
|
};
|
2012-10-31 13:41:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
/* Modify a stdenv so that it produces debug builds; that is,
|
|
|
|
binaries have debug info, and compiler optimisations are
|
|
|
|
disabled. */
|
|
|
|
keepDebugInfo = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
dontStrip = true;
|
2015-08-10 09:10:35 +02:00
|
|
|
NIX_CFLAGS_COMPILE = toString (args.NIX_CFLAGS_COMPILE or "") + " -ggdb -Og";
|
2012-10-31 13:41:54 +01:00
|
|
|
});
|
|
|
|
};
|
|
|
|
|
2014-02-04 16:58:12 +01:00
|
|
|
|
2014-10-10 14:01:38 +02:00
|
|
|
/* Modify a stdenv so that it uses the Gold linker. */
|
|
|
|
useGoldLinker = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
2015-05-04 14:00:12 +02:00
|
|
|
NIX_CFLAGS_LINK = toString (args.NIX_CFLAGS_LINK or "") + " -fuse-ld=gold";
|
2014-10-10 14:01:38 +02:00
|
|
|
});
|
|
|
|
};
|
2009-03-30 15:22:19 +02:00
|
|
|
}
|