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. */
|
|
|
|
|
|
|
|
{dietlibc, fetchurl, runCommand}:
|
|
|
|
|
|
|
|
|
|
|
|
rec {
|
|
|
|
|
|
|
|
|
|
|
|
# Override the compiler in stdenv for specific packages.
|
|
|
|
overrideGCC = stdenv: gcc: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // { NIX_GCC = gcc; });
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
# Add some arbitrary packages to buildInputs for specific packages.
|
|
|
|
# Used to override packages in stenv like Make. Should not be used
|
|
|
|
# for other dependencies.
|
|
|
|
overrideInStdenv = stdenv: pkgs: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args //
|
|
|
|
{ buildInputs = (if args ? buildInputs then args.buildInputs else []) ++ pkgs; }
|
|
|
|
);
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
# 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;
|
|
|
|
# };
|
|
|
|
overrideSetup = stdenv: setup: stdenv.regenerate setup;
|
|
|
|
|
|
|
|
|
|
|
|
# Return a modified stdenv that uses dietlibc to create small
|
|
|
|
# statically linked binaries.
|
|
|
|
useDietLibC = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
NIX_CFLAGS_LINK = "-static";
|
|
|
|
|
|
|
|
# libcompat.a contains some commonly used functions.
|
|
|
|
NIX_LDFLAGS = "-lcompat";
|
|
|
|
|
|
|
|
# These are added *after* the command-line flags, so we'll
|
|
|
|
# always optimise for size.
|
|
|
|
NIX_CFLAGS_COMPILE =
|
|
|
|
(if args ? NIX_CFLAGS_COMPILE then args.NIX_CFLAGS_COMPILE else "")
|
|
|
|
+ " -Os -s -D_BSD_SOURCE=1";
|
|
|
|
|
|
|
|
configureFlags =
|
|
|
|
(if args ? configureFlags then args.configureFlags else "")
|
|
|
|
+ " --disable-shared"; # brrr...
|
|
|
|
|
|
|
|
NIX_GCC = import ../build-support/gcc-wrapper {
|
|
|
|
inherit stdenv;
|
|
|
|
libc = dietlibc;
|
2009-06-22 16:26:14 +02:00
|
|
|
inherit (stdenv.gcc) gcc binutils nativeTools nativePrefix;
|
2009-02-10 16:48:30 +01:00
|
|
|
nativeLibc = false;
|
|
|
|
};
|
|
|
|
});
|
|
|
|
isDietLibC = true;
|
|
|
|
} // {inherit fetchurl;};
|
|
|
|
|
|
|
|
|
|
|
|
# Return a modified stdenv that uses klibc to create small
|
|
|
|
# statically linked binaries.
|
|
|
|
useKlibc = stdenv: klibc: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
NIX_CFLAGS_LINK = "-static";
|
|
|
|
|
|
|
|
# These are added *after* the command-line flags, so we'll
|
|
|
|
# always optimise for size.
|
|
|
|
NIX_CFLAGS_COMPILE =
|
|
|
|
(if args ? NIX_CFLAGS_COMPILE then args.NIX_CFLAGS_COMPILE else "")
|
|
|
|
+ " -Os -s";
|
|
|
|
|
|
|
|
configureFlags =
|
|
|
|
(if args ? configureFlags then args.configureFlags else "")
|
|
|
|
+ " --disable-shared"; # brrr...
|
|
|
|
|
|
|
|
NIX_GCC = runCommand "klibc-wrapper" {} ''
|
|
|
|
ensureDir $out/bin
|
|
|
|
ln -s ${klibc}/bin/klcc $out/bin/gcc
|
|
|
|
ln -s ${klibc}/bin/klcc $out/bin/cc
|
|
|
|
ensureDir $out/nix-support
|
|
|
|
echo 'PATH=$PATH:${stdenv.gcc.binutils}/bin' > $out/nix-support/setup-hook
|
|
|
|
'';
|
|
|
|
});
|
|
|
|
isKlibc = true;
|
|
|
|
isStatic = true;
|
|
|
|
} // {inherit fetchurl;};
|
|
|
|
|
|
|
|
|
|
|
|
# Return a modified stdenv that tries to build statically linked
|
|
|
|
# binaries.
|
|
|
|
makeStaticBinaries = stdenv: stdenv //
|
|
|
|
{ mkDerivation = args: stdenv.mkDerivation (args // {
|
|
|
|
NIX_CFLAGS_LINK = "-static";
|
|
|
|
|
|
|
|
configureFlags =
|
|
|
|
(if args ? configureFlags then args.configureFlags else "")
|
|
|
|
+ " --disable-shared"; # brrr...
|
|
|
|
});
|
|
|
|
isStatic = true;
|
|
|
|
} // {inherit fetchurl;};
|
|
|
|
|
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 //
|
2009-11-20 13:33:43 +01:00
|
|
|
{ mkDerivation = {name ? "", buildInputs ? [], buildNativeInputs ? [],
|
2009-11-20 17:38:01 +01:00
|
|
|
propagatedBuildInputs ? [], propagatedBuildNativeInputs ? [],
|
2009-11-22 23:48:43 +01:00
|
|
|
selfBuildNativeInput ? 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.
|
|
|
|
|
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining
the cross compilation functionality.
- I renamed some expected stdenv.mkDerivation parameter attributes so we can
keep this branch properly updated from trunk. We agreed with Nicolas Pierron
doing a massive renaming, so all current buildInputs become hostInputs (input
as build for the host machine, in autotools terminology) , and
then buildInputs would mean "input as for the build machine".
By now, the specific "input as for the build machine" is specified through
buildNativeInputs. We should fix this in the merge to trunk.
- I made the generic stdenv understand the buildNativeInputs, otherwise if
we start changing nixpkgs expressions so they distinguish the current
buildInputs into buildInputs and buildNativeInputs, we could break even more
nixpkgs for other platforms.
- I changed the default result of mkDerivation so it becomes the derivation for
to be run in the build machine. This allows, without any special rewriting,
"fetchurl" derivations to be always results for the build machine to use
them.
- The change above implies that, for anyone wanting to cross-compile, has to
build the hostDrv of the wanted derivation. For example, after this commit,
the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described
the contents of this arm.nix in r18398.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
|
|
|
getBuildDrv = drv : if (drv ? buildDrv) then drv.buildDrv else drv;
|
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
|
|
|
buildNativeInputsDrvs = map (getBuildDrv) buildNativeInputs;
|
|
|
|
buildInputsDrvs = map (drv: drv.hostDrv) buildInputs;
|
|
|
|
buildInputsDrvsAsBuildInputs = map (getBuildDrv) buildInputs;
|
|
|
|
propagatedBuildInputsDrvs = map (drv: drv.hostDrv) (propagatedBuildInputs);
|
|
|
|
propagatedBuildNativeInputsDrvs = map (drv: drv.buildDrv)
|
|
|
|
(propagatedBuildNativeInputs);
|
|
|
|
|
|
|
|
# The base stdenv already knows that buildNativeInputs and
|
|
|
|
# buildInputs should be built with the usual gcc-wrapper
|
|
|
|
# And the same for propagatedBuildInputs.
|
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining
the cross compilation functionality.
- I renamed some expected stdenv.mkDerivation parameter attributes so we can
keep this branch properly updated from trunk. We agreed with Nicolas Pierron
doing a massive renaming, so all current buildInputs become hostInputs (input
as build for the host machine, in autotools terminology) , and
then buildInputs would mean "input as for the build machine".
By now, the specific "input as for the build machine" is specified through
buildNativeInputs. We should fix this in the merge to trunk.
- I made the generic stdenv understand the buildNativeInputs, otherwise if
we start changing nixpkgs expressions so they distinguish the current
buildInputs into buildInputs and buildNativeInputs, we could break even more
nixpkgs for other platforms.
- I changed the default result of mkDerivation so it becomes the derivation for
to be run in the build machine. This allows, without any special rewriting,
"fetchurl" derivations to be always results for the build machine to use
them.
- The change above implies that, for anyone wanting to cross-compile, has to
build the hostDrv of the wanted derivation. For example, after this commit,
the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described
the contents of this arm.nix in r18398.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
|
|
|
buildDrv = 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
|
|
|
|
# buildNativeInput.
|
|
|
|
hostAsBuildDrv = drv: builtins.unsafeDiscardStringContext
|
|
|
|
drv.buildDrv.drvPath == builtins.unsafeDiscardStringContext
|
|
|
|
drv.hostDrv.drvPath;
|
|
|
|
nativeInputsFromBuildInputs = stdenv.lib.filter (hostAsBuildDrv) buildInputs;
|
|
|
|
|
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
|
|
|
# We should overwrite the input attributes in hostDrv, to overwrite
|
|
|
|
# the defaults for only-native builds in the base stdenv
|
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
|
|
|
hostDrv = if (cross == null) then buildDrv else
|
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining
the cross compilation functionality.
- I renamed some expected stdenv.mkDerivation parameter attributes so we can
keep this branch properly updated from trunk. We agreed with Nicolas Pierron
doing a massive renaming, so all current buildInputs become hostInputs (input
as build for the host machine, in autotools terminology) , and
then buildInputs would mean "input as for the build machine".
By now, the specific "input as for the build machine" is specified through
buildNativeInputs. We should fix this in the merge to trunk.
- I made the generic stdenv understand the buildNativeInputs, otherwise if
we start changing nixpkgs expressions so they distinguish the current
buildInputs into buildInputs and buildNativeInputs, we could break even more
nixpkgs for other platforms.
- I changed the default result of mkDerivation so it becomes the derivation for
to be run in the build machine. This allows, without any special rewriting,
"fetchurl" derivations to be always results for the build machine to use
them.
- The change above implies that, for anyone wanting to cross-compile, has to
build the hostDrv of the wanted derivation. For example, after this commit,
the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described
the contents of this arm.nix in r18398.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
|
|
|
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;
|
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
|
|
|
buildNativeInputs = buildNativeInputsDrvs
|
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
|
2009-11-20 17:38:01 +01:00
|
|
|
++ [ gccCross binutilsCross ] ++
|
2009-11-22 23:48:43 +01:00
|
|
|
stdenv.lib.optional selfBuildNativeInput buildDrv;
|
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 = [];
|
|
|
|
propagatedBuildInputs = propagatedBuildInputsDrvs +
|
|
|
|
buildInputsDrvs;
|
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
|
|
|
propagatedBuildNativeInputs = propagatedBuildNativeInputsDrvs;
|
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;
|
|
|
|
});
|
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining
the cross compilation functionality.
- I renamed some expected stdenv.mkDerivation parameter attributes so we can
keep this branch properly updated from trunk. We agreed with Nicolas Pierron
doing a massive renaming, so all current buildInputs become hostInputs (input
as build for the host machine, in autotools terminology) , and
then buildInputs would mean "input as for the build machine".
By now, the specific "input as for the build machine" is specified through
buildNativeInputs. We should fix this in the merge to trunk.
- I made the generic stdenv understand the buildNativeInputs, otherwise if
we start changing nixpkgs expressions so they distinguish the current
buildInputs into buildInputs and buildNativeInputs, we could break even more
nixpkgs for other platforms.
- I changed the default result of mkDerivation so it becomes the derivation for
to be run in the build machine. This allows, without any special rewriting,
"fetchurl" derivations to be always results for the build machine to use
them.
- The change above implies that, for anyone wanting to cross-compile, has to
build the hostDrv of the wanted derivation. For example, after this commit,
the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described
the contents of this arm.nix in r18398.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
|
|
|
in buildDrv // {
|
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
|
|
|
inherit hostDrv buildDrv;
|
|
|
|
};
|
|
|
|
} // { inherit cross; };
|
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-09-01 23:56:46 +02:00
|
|
|
/* Return a modified stdenv that perfoms the build under $out/.build
|
|
|
|
instead of in $TMPDIR. Thus, the sources are kept available.
|
|
|
|
This is useful for things like debugging or generation of
|
|
|
|
dynamic analysis reports. */
|
|
|
|
keepBuildTree = stdenv:
|
|
|
|
addAttrsToDerivation
|
|
|
|
{ prePhases = "moveBuildDir";
|
|
|
|
|
|
|
|
moveBuildDir =
|
|
|
|
''
|
|
|
|
ensureDir $out/.build
|
|
|
|
cd $out/.build
|
|
|
|
'';
|
|
|
|
} stdenv;
|
|
|
|
|
|
|
|
|
2009-09-02 08:31:13 +02:00
|
|
|
cleanupBuildTree = stdenv:
|
|
|
|
addAttrsToDerivation
|
|
|
|
{ postPhases = "cleanupBuildDir";
|
|
|
|
|
|
|
|
# Get rid of everything that isn't a gcno file or a C source
|
|
|
|
# file. This also includes the gcda files; we're not
|
|
|
|
# interested in coverage resulting from the package's own test
|
|
|
|
# suite.
|
|
|
|
cleanupBuildDir =
|
|
|
|
''
|
|
|
|
find $out/.build/ -type f -a ! \
|
|
|
|
\( -name "*.c" -o -name "*.h" -o -name "*.gcno" \) \
|
|
|
|
| xargs rm -f --
|
|
|
|
'';
|
|
|
|
} stdenv;
|
|
|
|
|
|
|
|
|
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:
|
|
|
|
addAttrsToDerivation
|
|
|
|
{ NIX_CFLAGS_COMPILE = "-O0 --coverage";
|
|
|
|
|
|
|
|
# This is an uberhack to prevent libtool from removing gcno
|
|
|
|
# files. This has been fixed in libtool, but there are
|
|
|
|
# packages out there with old ltmain.sh scripts.
|
|
|
|
# See http://www.mail-archive.com/libtool@gnu.org/msg10725.html
|
|
|
|
postUnpack =
|
|
|
|
''
|
|
|
|
for i in $(find -name ltmain.sh); do
|
|
|
|
substituteInPlace $i --replace '*.$objext)' '*.$objext | *.gcno)'
|
|
|
|
done
|
|
|
|
'';
|
|
|
|
}
|
2009-09-01 23:56:46 +02:00
|
|
|
|
|
|
|
# Object files instrumented with coverage analysis write
|
|
|
|
# runtime coverage data to <path>/<object>.gcda, where <path>
|
|
|
|
# is the location where gcc originally created the object
|
|
|
|
# file. That would be /tmp/nix-build-<something>, which will
|
|
|
|
# be long gone by the time we run the program. Furthermore,
|
|
|
|
# the <object>.gcno files created at compile time are also
|
|
|
|
# written there. And to make nice coverage reports with lcov,
|
|
|
|
# we need the source code. So we have to use the
|
|
|
|
# `keepBuildTree' adapter as well.
|
2009-09-02 08:31:13 +02:00
|
|
|
(cleanupBuildTree (keepBuildTree stdenv));
|
2009-09-01 23:56:46 +02: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:
|
|
|
|
pkgs.lib.recursiveUpdate
|
|
|
|
(stdenv.mkDerivation args)
|
|
|
|
{ meta.maintainers = maintainers; };
|
|
|
|
};
|
2009-03-30 15:22:19 +02:00
|
|
|
}
|