2017-08-09 07:20:56 +02:00
|
|
|
|
set -eu
|
2014-10-10 11:50:25 +02:00
|
|
|
|
set -o pipefail
|
2021-09-26 14:05:10 +02:00
|
|
|
|
shopt -s inherit_errexit
|
2014-07-01 16:17:23 +02:00
|
|
|
|
|
2021-08-19 16:23:58 +02:00
|
|
|
|
if [[ -n "${BASH_VERSINFO-}" && "${BASH_VERSINFO-}" -lt 4 ]]; then
|
2021-01-01 07:22:23 +01:00
|
|
|
|
echo "Detected Bash version that isn't supported by Nixpkgs (${BASH_VERSION})"
|
|
|
|
|
echo "Please install Bash 4 or greater to continue."
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
|
|
|
|
|
2017-09-20 01:11:29 +02:00
|
|
|
|
if (( "${NIX_DEBUG:-0}" >= 6 )); then
|
|
|
|
|
set -x
|
|
|
|
|
fi
|
|
|
|
|
|
2014-06-25 16:47:58 +02:00
|
|
|
|
: ${outputs:=out}
|
|
|
|
|
|
|
|
|
|
|
2014-06-25 15:38:37 +02:00
|
|
|
|
######################################################################
|
|
|
|
|
# Hook handling.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Run all hooks with the specified name in the order in which they
|
|
|
|
|
# were added, stopping if any fails (returns a non-zero exit
|
2014-07-08 13:47:09 +02:00
|
|
|
|
# code). The hooks for <hookName> are the shell function or variable
|
|
|
|
|
# <hookName>, and the values of the shell array ‘<hookName>Hooks’.
|
2014-06-25 15:38:37 +02:00
|
|
|
|
runHook() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local hookName="$1"
|
2014-07-08 14:14:28 +02:00
|
|
|
|
shift
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local hooksSlice="${hookName%Hook}Hooks[@]"
|
2017-07-25 23:48:50 +02:00
|
|
|
|
|
2017-07-07 01:29:48 +02:00
|
|
|
|
local hook
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# Hack around old bash being bad and thinking empty arrays are
|
|
|
|
|
# undefined.
|
|
|
|
|
for hook in "_callImplicitHook 0 $hookName" ${!hooksSlice+"${!hooksSlice}"}; do
|
2015-05-12 18:41:02 +02:00
|
|
|
|
_eval "$hook" "$@"
|
2014-06-25 15:38:37 +02:00
|
|
|
|
done
|
2017-08-09 07:20:56 +02:00
|
|
|
|
|
2014-06-25 15:38:37 +02:00
|
|
|
|
return 0
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2014-06-30 13:48:29 +02:00
|
|
|
|
# Run all hooks with the specified name, until one succeeds (returns a
|
|
|
|
|
# zero exit code). If none succeed, return a non-zero exit code.
|
|
|
|
|
runOneHook() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local hookName="$1"
|
2014-07-08 14:14:28 +02:00
|
|
|
|
shift
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local hooksSlice="${hookName%Hook}Hooks[@]"
|
2017-07-25 23:48:50 +02:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local hook ret=1
|
|
|
|
|
# Hack around old bash like above
|
|
|
|
|
for hook in "_callImplicitHook 1 $hookName" ${!hooksSlice+"${!hooksSlice}"}; do
|
2014-07-08 14:14:28 +02:00
|
|
|
|
if _eval "$hook" "$@"; then
|
2017-08-09 07:20:56 +02:00
|
|
|
|
ret=0
|
|
|
|
|
break
|
2014-06-30 13:48:29 +02:00
|
|
|
|
fi
|
|
|
|
|
done
|
2017-08-09 07:20:56 +02:00
|
|
|
|
|
|
|
|
|
return "$ret"
|
2014-06-30 13:48:29 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
# Run the named hook, either by calling the function with that name or
|
2014-06-25 15:38:37 +02:00
|
|
|
|
# by evaluating the variable with that name. This allows convenient
|
2009-02-01 22:28:02 +01:00
|
|
|
|
# setting of hooks both from Nix expressions (as attributes /
|
2014-06-25 15:38:37 +02:00
|
|
|
|
# environment variables) and from shell scripts (as functions). If you
|
|
|
|
|
# want to allow multiple hooks, use runHook instead.
|
2014-06-30 13:48:29 +02:00
|
|
|
|
_callImplicitHook() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local def="$1"
|
|
|
|
|
local hookName="$2"
|
2019-09-19 17:06:48 +02:00
|
|
|
|
if declare -F "$hookName" > /dev/null; then
|
|
|
|
|
"$hookName"
|
|
|
|
|
elif type -p "$hookName" > /dev/null; then
|
|
|
|
|
source "$hookName"
|
|
|
|
|
elif [ -n "${!hookName:-}" ]; then
|
|
|
|
|
eval "${!hookName}"
|
|
|
|
|
else
|
|
|
|
|
return "$def"
|
|
|
|
|
fi
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# `_eval` expects hook to need nounset disable and leave it
|
|
|
|
|
# disabled anyways, so Ok to to delegate. The alternative of a
|
|
|
|
|
# return trap is no good because it would affect nested returns.
|
2009-02-01 22:28:02 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2014-06-25 15:38:37 +02:00
|
|
|
|
# A function wrapper around ‘eval’ that ensures that ‘return’ inside
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# hooks exits the hook, not the caller. Also will only pass args if
|
|
|
|
|
# command can take them
|
2014-06-25 15:38:37 +02:00
|
|
|
|
_eval() {
|
2019-09-19 11:43:34 +02:00
|
|
|
|
if declare -F "$1" > /dev/null 2>&1; then
|
2017-08-09 07:20:56 +02:00
|
|
|
|
"$@" # including args
|
2014-07-08 14:14:28 +02:00
|
|
|
|
else
|
2017-08-09 07:20:56 +02:00
|
|
|
|
eval "$1"
|
2014-07-08 14:14:28 +02:00
|
|
|
|
fi
|
2014-06-25 15:38:37 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2015-06-15 11:24:11 +02:00
|
|
|
|
######################################################################
|
|
|
|
|
# Logging.
|
|
|
|
|
|
2017-07-24 14:25:57 +02:00
|
|
|
|
# Obsolete.
|
|
|
|
|
stopNest() { true; }
|
|
|
|
|
header() { echo "$1"; }
|
|
|
|
|
closeNest() { true; }
|
2015-06-15 11:24:11 +02:00
|
|
|
|
|
2017-07-13 22:31:39 +02:00
|
|
|
|
# Prints a command such that all word splits are unambiguous. We need
|
|
|
|
|
# to split the command in three parts because the middle format string
|
|
|
|
|
# will be, and must be, repeated for each argument. The first argument
|
|
|
|
|
# goes before the ':' and is just for convenience.
|
|
|
|
|
echoCmd() {
|
|
|
|
|
printf "%s:" "$1"
|
|
|
|
|
shift
|
|
|
|
|
printf ' %q' "$@"
|
|
|
|
|
echo
|
|
|
|
|
}
|
|
|
|
|
|
2015-06-15 11:24:11 +02:00
|
|
|
|
|
2014-06-25 15:38:37 +02:00
|
|
|
|
######################################################################
|
|
|
|
|
# Error handling.
|
|
|
|
|
|
2008-04-23 09:19:48 +02:00
|
|
|
|
exitHandler() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
exitCode="$?"
|
2008-04-23 09:19:48 +02:00
|
|
|
|
set +e
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${showBuildStats:-}" ]; then
|
2021-09-06 05:05:15 +02:00
|
|
|
|
read -r -d '' -a buildTimes < <(times)
|
|
|
|
|
echo "build times:"
|
|
|
|
|
echo "user time for the shell ${buildTimes[0]}"
|
|
|
|
|
echo "system time for the shell ${buildTimes[1]}"
|
|
|
|
|
echo "user time for all child processes ${buildTimes[2]}"
|
|
|
|
|
echo "system time for all child processes ${buildTimes[3]}"
|
2008-04-23 09:19:48 +02:00
|
|
|
|
fi
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if (( "$exitCode" != 0 )); then
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook failureHook
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2008-04-23 09:19:48 +02:00
|
|
|
|
# If the builder had a non-zero exit code and
|
|
|
|
|
# $succeedOnFailure is set, create the file
|
2015-08-03 20:03:11 +02:00
|
|
|
|
# ‘$out/nix-support/failed’ to signal failure, and exit
|
2008-04-23 09:19:48 +02:00
|
|
|
|
# normally. Otherwise, return the original exit code.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${succeedOnFailure:-}" ]; then
|
2008-04-23 09:19:48 +02:00
|
|
|
|
echo "build failed with exit code $exitCode (ignored)"
|
2012-01-18 21:16:00 +01:00
|
|
|
|
mkdir -p "$out/nix-support"
|
2017-07-16 18:10:52 +02:00
|
|
|
|
printf "%s" "$exitCode" > "$out/nix-support/failed"
|
2008-04-23 09:19:48 +02:00
|
|
|
|
exit 0
|
|
|
|
|
fi
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2008-04-23 09:19:48 +02:00
|
|
|
|
else
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook exitHook
|
2008-04-23 09:19:48 +02:00
|
|
|
|
fi
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2017-07-16 18:10:52 +02:00
|
|
|
|
exit "$exitCode"
|
2008-04-23 09:19:48 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
trap "exitHandler" EXIT
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
######################################################################
|
2014-07-01 16:17:23 +02:00
|
|
|
|
# Helper functions.
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2007-11-17 15:34:27 +01:00
|
|
|
|
|
|
|
|
|
addToSearchPathWithCustomDelimiter() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local delimiter="$1"
|
|
|
|
|
local varName="$2"
|
|
|
|
|
local dir="$3"
|
2021-03-13 19:58:21 +01:00
|
|
|
|
if [[ -d "$dir" && "${!varName:+${delimiter}${!varName}${delimiter}}" \
|
|
|
|
|
!= *"${delimiter}${dir}${delimiter}"* ]]; then
|
2017-08-09 07:20:56 +02:00
|
|
|
|
export "${varName}=${!varName:+${!varName}${delimiter}}${dir}"
|
2007-11-17 15:34:49 +01:00
|
|
|
|
fi
|
2007-11-17 15:34:27 +01:00
|
|
|
|
}
|
|
|
|
|
|
2008-04-23 09:19:48 +02:00
|
|
|
|
addToSearchPath() {
|
2019-03-03 02:02:45 +01:00
|
|
|
|
addToSearchPathWithCustomDelimiter ":" "$@"
|
2007-11-17 15:34:27 +01:00
|
|
|
|
}
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2014-08-25 15:30:46 +02:00
|
|
|
|
# Add $1/lib* into rpaths.
|
|
|
|
|
# The function is used in multiple-outputs.sh hook,
|
|
|
|
|
# so it is defined here but tried after the hook.
|
|
|
|
|
_addRpathPrefix() {
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ "${NIX_NO_SELF_RPATH:-0}" != 1 ]; then
|
2019-10-30 00:43:34 +01:00
|
|
|
|
export NIX_LDFLAGS="-rpath $1/lib ${NIX_LDFLAGS-}"
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${NIX_LIB64_IN_SELF_RPATH:-}" ]; then
|
2019-10-30 00:43:34 +01:00
|
|
|
|
export NIX_LDFLAGS="-rpath $1/lib64 ${NIX_LDFLAGS-}"
|
2014-08-25 15:30:46 +02:00
|
|
|
|
fi
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${NIX_LIB32_IN_SELF_RPATH:-}" ]; then
|
2019-10-30 00:43:34 +01:00
|
|
|
|
export NIX_LDFLAGS="-rpath $1/lib32 ${NIX_LDFLAGS-}"
|
2014-08-25 15:30:46 +02:00
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
}
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2016-02-18 22:52:44 +01:00
|
|
|
|
# Return success if the specified file is an ELF object.
|
|
|
|
|
isELF() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local fn="$1"
|
2017-06-30 02:28:27 +02:00
|
|
|
|
local fd
|
2016-02-18 22:52:44 +01:00
|
|
|
|
local magic
|
|
|
|
|
exec {fd}< "$fn"
|
2017-07-16 18:10:52 +02:00
|
|
|
|
read -r -n 4 -u "$fd" magic
|
2016-02-18 22:52:44 +01:00
|
|
|
|
exec {fd}<&-
|
2018-09-23 20:32:19 +02:00
|
|
|
|
if [ "$magic" = $'\177ELF' ]; then return 0; else return 1; fi
|
2016-02-18 22:52:44 +01:00
|
|
|
|
}
|
|
|
|
|
|
2021-09-18 05:09:06 +02:00
|
|
|
|
# Return success if the specified file is a Mach-O object.
|
|
|
|
|
isMachO() {
|
|
|
|
|
local fn="$1"
|
|
|
|
|
local fd
|
|
|
|
|
local magic
|
|
|
|
|
exec {fd}< "$fn"
|
|
|
|
|
read -r -n 4 -u "$fd" magic
|
|
|
|
|
exec {fd}<&-
|
|
|
|
|
|
|
|
|
|
# nix uses 'declare -F' in get-env.sh to retrieve the loaded functions.
|
|
|
|
|
# If we use the $'string' syntax instead of 'echo -ne' then 'declare' will print the raw characters and break nix.
|
|
|
|
|
# See https://github.com/NixOS/nixpkgs/pull/138334 and https://github.com/NixOS/nix/issues/5262.
|
|
|
|
|
|
|
|
|
|
# https://opensource.apple.com/source/lldb/lldb-310.2.36/examples/python/mach_o.py.auto.html
|
|
|
|
|
if [[ "$magic" = $(echo -ne "\xfe\xed\xfa\xcf") || "$magic" = $(echo -ne "\xcf\xfa\xed\xfe") ]]; then
|
|
|
|
|
# MH_MAGIC_64 || MH_CIGAM_64
|
|
|
|
|
return 0;
|
|
|
|
|
elif [[ "$magic" = $(echo -ne "\xfe\xed\xfa\xce") || "$magic" = $(echo -ne "\xce\xfa\xed\xfe") ]]; then
|
|
|
|
|
# MH_MAGIC || MH_CIGAM
|
|
|
|
|
return 0;
|
|
|
|
|
elif [[ "$magic" = $(echo -ne "\xca\xfe\xba\xbe") || "$magic" = $(echo -ne "\xbe\xba\xfe\xca") ]]; then
|
|
|
|
|
# FAT_MAGIC || FAT_CIGAM
|
|
|
|
|
return 0;
|
|
|
|
|
else
|
|
|
|
|
return 1;
|
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
2017-05-04 20:06:40 +02:00
|
|
|
|
# Return success if the specified file is a script (i.e. starts with
|
|
|
|
|
# "#!").
|
|
|
|
|
isScript() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local fn="$1"
|
2017-06-30 02:28:27 +02:00
|
|
|
|
local fd
|
2017-05-04 20:06:40 +02:00
|
|
|
|
local magic
|
|
|
|
|
exec {fd}< "$fn"
|
2017-07-16 18:10:52 +02:00
|
|
|
|
read -r -n 2 -u "$fd" magic
|
2017-05-04 20:06:40 +02:00
|
|
|
|
exec {fd}<&-
|
2017-07-16 18:10:52 +02:00
|
|
|
|
if [[ "$magic" =~ \#! ]]; then return 0; else return 1; fi
|
2017-05-04 20:06:40 +02:00
|
|
|
|
}
|
|
|
|
|
|
2017-07-10 17:59:14 +02:00
|
|
|
|
# printf unfortunately will print a trailing newline regardless
|
|
|
|
|
printLines() {
|
2017-11-17 19:26:21 +01:00
|
|
|
|
(( "$#" > 0 )) || return 0
|
2017-07-10 17:59:14 +02:00
|
|
|
|
printf '%s\n' "$@"
|
|
|
|
|
}
|
2016-02-18 22:52:44 +01:00
|
|
|
|
|
2017-07-26 00:48:47 +02:00
|
|
|
|
printWords() {
|
2017-11-17 19:26:21 +01:00
|
|
|
|
(( "$#" > 0 )) || return 0
|
2017-07-26 00:48:47 +02:00
|
|
|
|
printf '%s ' "$@"
|
|
|
|
|
}
|
|
|
|
|
|
2014-07-01 16:17:23 +02:00
|
|
|
|
######################################################################
|
|
|
|
|
# Initialisation.
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
|
|
|
|
|
2020-06-08 12:52:58 +02:00
|
|
|
|
# Set a fallback default value for SOURCE_DATE_EPOCH, used by some build tools
|
|
|
|
|
# to provide a deterministic substitute for the "current" time. Note that
|
|
|
|
|
# 315532800 = 1980-01-01 12:00:00. We use this date because python's wheel
|
|
|
|
|
# implementation uses zip archive and zip does not support dates going back to
|
|
|
|
|
# 1970.
|
2015-12-03 11:49:32 +01:00
|
|
|
|
export SOURCE_DATE_EPOCH
|
2020-06-08 12:52:58 +02:00
|
|
|
|
: ${SOURCE_DATE_EPOCH:=315532800}
|
2015-12-03 11:49:32 +01:00
|
|
|
|
|
|
|
|
|
|
2009-04-19 00:22:51 +02:00
|
|
|
|
# Wildcard expansions that don't match should expand to an empty list.
|
|
|
|
|
# This ensures that, for instance, "for i in *; do ...; done" does the
|
|
|
|
|
# right thing.
|
|
|
|
|
shopt -s nullglob
|
|
|
|
|
|
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
# Set up the initial path.
|
|
|
|
|
PATH=
|
2018-11-14 19:41:50 +01:00
|
|
|
|
HOST_PATH=
|
2014-07-01 17:39:07 +02:00
|
|
|
|
for i in $initialPath; do
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ "$i" = / ]; then i=; fi
|
2017-07-16 18:10:52 +02:00
|
|
|
|
addToSearchPath PATH "$i/bin"
|
2018-11-14 19:41:50 +01:00
|
|
|
|
|
|
|
|
|
# For backward compatibility, we add initial path to HOST_PATH so
|
|
|
|
|
# it can be used in auto patch-shebangs. Unfortunately this will
|
|
|
|
|
# not work with cross compilation.
|
|
|
|
|
if [ -z "${strictDeps-}" ]; then
|
|
|
|
|
addToSearchPath HOST_PATH "$i/bin"
|
|
|
|
|
fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
done
|
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
unset i
|
|
|
|
|
|
2017-09-20 01:10:49 +02:00
|
|
|
|
if (( "${NIX_DEBUG:-0}" >= 1 )); then
|
2008-02-21 00:02:41 +01:00
|
|
|
|
echo "initial path: $PATH"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Check that the pre-hook initialised SHELL.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${SHELL:-}" ]; then echo "SHELL not set"; exit 1; fi
|
2017-07-16 18:10:52 +02:00
|
|
|
|
BASH="$SHELL"
|
|
|
|
|
export CONFIG_SHELL="$SHELL"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2016-05-25 19:36:50 +02:00
|
|
|
|
|
2014-07-01 17:39:07 +02:00
|
|
|
|
# Execute the pre-hook.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${shell:-}" ]; then export shell="$SHELL"; fi
|
2014-11-06 11:26:09 +01:00
|
|
|
|
runHook preHook
|
2014-07-01 17:39:07 +02:00
|
|
|
|
|
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
# Allow the caller to augment buildInputs (it's not always possible to
|
|
|
|
|
# do this before the call to setup.sh, since the PATH is empty at that
|
|
|
|
|
# point; here we have a basic Unix environment).
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook addInputsHook
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Package accumulators
|
|
|
|
|
|
|
|
|
|
# shellcheck disable=SC2034
|
|
|
|
|
declare -a pkgsBuildBuild pkgsBuildHost pkgsBuildTarget
|
|
|
|
|
declare -a pkgsHostHost pkgsHostTarget
|
|
|
|
|
declare -a pkgsTargetTarget
|
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a pkgBuildAccumVars=(pkgsBuildBuild pkgsBuildHost pkgsBuildTarget)
|
|
|
|
|
declare -a pkgHostAccumVars=(pkgsHostHost pkgsHostTarget)
|
|
|
|
|
declare -a pkgTargetAccumVars=(pkgsTargetTarget)
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a pkgAccumVarVars=(pkgBuildAccumVars pkgHostAccumVars pkgTargetAccumVars)
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Hooks
|
|
|
|
|
|
|
|
|
|
declare -a envBuildBuildHooks envBuildHostHooks envBuildTargetHooks
|
|
|
|
|
declare -a envHostHostHooks envHostTargetHooks
|
|
|
|
|
declare -a envTargetTargetHooks
|
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a pkgBuildHookVars=(envBuildBuildHook envBuildHostHook envBuildTargetHook)
|
|
|
|
|
declare -a pkgHostHookVars=(envHostHostHook envHostTargetHook)
|
|
|
|
|
declare -a pkgTargetHookVars=(envTargetTargetHook)
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a pkgHookVarVars=(pkgBuildHookVars pkgHostHookVars pkgTargetHookVars)
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
2021-07-19 07:55:56 +02:00
|
|
|
|
# those variables are declared here, since where and if they are used varies
|
|
|
|
|
# shellcheck disable=SC2034
|
|
|
|
|
declare -a preFixupHooks fixupOutputHooks preConfigureHooks postFixupHooks postUnpackHooks unpackCmdHooks
|
|
|
|
|
|
2017-08-03 18:45:06 +02:00
|
|
|
|
# Add env hooks for all sorts of deps with the specified host offset.
|
|
|
|
|
addEnvHooks() {
|
|
|
|
|
local depHostOffset="$1"
|
|
|
|
|
shift
|
|
|
|
|
local pkgHookVarsSlice="${pkgHookVarVars[$depHostOffset + 1]}[@]"
|
|
|
|
|
local pkgHookVar
|
|
|
|
|
for pkgHookVar in "${!pkgHookVarsSlice}"; do
|
|
|
|
|
eval "${pkgHookVar}s"'+=("$@")'
|
|
|
|
|
done
|
|
|
|
|
}
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Propagated dep files
|
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a propagatedBuildDepFiles=(
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
propagated-build-build-deps
|
|
|
|
|
propagated-native-build-inputs # Legacy name for back-compat
|
|
|
|
|
propagated-build-target-deps
|
|
|
|
|
)
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a propagatedHostDepFiles=(
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
propagated-host-host-deps
|
|
|
|
|
propagated-build-inputs # Legacy name for back-compat
|
|
|
|
|
)
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a propagatedTargetDepFiles=(
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
propagated-target-target-deps
|
|
|
|
|
)
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a propagatedDepFilesVars=(
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
propagatedBuildDepFiles
|
|
|
|
|
propagatedHostDepFiles
|
|
|
|
|
propagatedTargetDepFiles
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# Platform offsets: build = -1, host = 0, target = 1
|
2019-09-27 00:47:38 +02:00
|
|
|
|
declare -a allPlatOffsets=(-1 0 1)
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Mutually-recursively find all build inputs. See the dependency section of the
|
|
|
|
|
# stdenv chapter of the Nixpkgs manual for the specification this algorithm
|
|
|
|
|
# implements.
|
2008-04-23 09:19:48 +02:00
|
|
|
|
findInputs() {
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local -r pkg="$1"
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local -r hostOffset="$2"
|
|
|
|
|
local -r targetOffset="$3"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Sanity check
|
2021-08-17 16:02:11 +02:00
|
|
|
|
(( hostOffset <= targetOffset )) || exit -1
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local varVar="${pkgAccumVarVars[hostOffset + 1]}"
|
|
|
|
|
local varRef="$varVar[$((targetOffset - hostOffset))]"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local var="${!varRef}"
|
|
|
|
|
unset -v varVar varRef
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2017-07-25 23:48:50 +02:00
|
|
|
|
# TODO(@Ericson2314): Restore using associative array once Darwin
|
|
|
|
|
# nix-shell doesn't use impure bash. This should replace the O(n)
|
|
|
|
|
# case with an O(1) hash map lookup, assuming bash is implemented
|
|
|
|
|
# well :D.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local varSlice="$var[*]"
|
|
|
|
|
# ${..-} to hack around old bash empty array problem
|
|
|
|
|
case "${!varSlice-}" in
|
2017-07-25 23:48:50 +02:00
|
|
|
|
*" $pkg "*) return 0 ;;
|
|
|
|
|
esac
|
2017-08-09 07:20:56 +02:00
|
|
|
|
unset -v varSlice
|
2017-07-25 23:48:50 +02:00
|
|
|
|
|
2017-07-26 02:58:47 +02:00
|
|
|
|
eval "$var"'+=("$pkg")'
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2015-06-15 11:24:55 +02:00
|
|
|
|
if ! [ -e "$pkg" ]; then
|
|
|
|
|
echo "build input $pkg does not exist" >&2
|
|
|
|
|
exit 1
|
2014-06-25 17:01:29 +02:00
|
|
|
|
fi
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# The current package's host and target offset together
|
|
|
|
|
# provide a <=-preserving homomorphism from the relative
|
|
|
|
|
# offsets to current offset
|
|
|
|
|
function mapOffset() {
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local -r inputOffset="$1"
|
2021-10-01 14:44:55 +02:00
|
|
|
|
local -n outputOffset="$2"
|
2021-08-17 16:02:11 +02:00
|
|
|
|
if (( inputOffset <= 0 )); then
|
2021-10-01 14:44:55 +02:00
|
|
|
|
outputOffset=$((inputOffset + hostOffset))
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
else
|
2021-10-01 14:44:55 +02:00
|
|
|
|
outputOffset=$((inputOffset - 1 + targetOffset))
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
# Host offset relative to that of the package whose immediate
|
|
|
|
|
# dependencies we are currently exploring.
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local relHostOffset
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
for relHostOffset in "${allPlatOffsets[@]}"; do
|
|
|
|
|
# `+ 1` so we start at 0 for valid index
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local files="${propagatedDepFilesVars[relHostOffset + 1]}"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Host offset relative to the package currently being
|
|
|
|
|
# built---as absolute an offset as will be used.
|
2021-10-01 14:44:55 +02:00
|
|
|
|
local hostOffsetNext
|
|
|
|
|
mapOffset "$relHostOffset" hostOffsetNext
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Ensure we're in bounds relative to the package currently
|
|
|
|
|
# being built.
|
2021-10-01 14:44:55 +02:00
|
|
|
|
(( -1 <= hostOffsetNext && hostOffsetNext <= 1 )) || continue
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Target offset relative to the *host* offset of the package
|
|
|
|
|
# whose immediate dependencies we are currently exploring.
|
2021-10-01 14:44:55 +02:00
|
|
|
|
local relTargetOffset
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
for relTargetOffset in "${allPlatOffsets[@]}"; do
|
|
|
|
|
(( "$relHostOffset" <= "$relTargetOffset" )) || continue
|
|
|
|
|
|
|
|
|
|
local fileRef="${files}[$relTargetOffset - $relHostOffset]"
|
|
|
|
|
local file="${!fileRef}"
|
|
|
|
|
unset -v fileRef
|
|
|
|
|
|
|
|
|
|
# Target offset relative to the package currently being
|
|
|
|
|
# built.
|
2021-10-01 14:44:55 +02:00
|
|
|
|
local targetOffsetNext
|
|
|
|
|
mapOffset "$relTargetOffset" targetOffsetNext
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Once again, ensure we're in bounds relative to the
|
|
|
|
|
# package currently being built.
|
2021-10-01 14:44:55 +02:00
|
|
|
|
(( -1 <= hostOffsetNext && hostOffsetNext <= 1 )) || continue
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
[[ -f "$pkg/nix-support/$file" ]] || continue
|
|
|
|
|
|
|
|
|
|
local pkgNext
|
2019-09-19 17:43:35 +02:00
|
|
|
|
read -r -d '' pkgNext < "$pkg/nix-support/$file" || true
|
|
|
|
|
for pkgNext in $pkgNext; do
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
findInputs "$pkgNext" "$hostOffsetNext" "$targetOffsetNext"
|
|
|
|
|
done
|
2017-11-08 19:43:28 +01:00
|
|
|
|
done
|
2017-11-17 19:26:21 +01:00
|
|
|
|
done
|
2017-11-08 19:43:28 +01:00
|
|
|
|
}
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Make sure all are at least defined as empty
|
|
|
|
|
: ${depsBuildBuild=} ${depsBuildBuildPropagated=}
|
|
|
|
|
: ${nativeBuildInputs=} ${propagatedNativeBuildInputs=} ${defaultNativeBuildInputs=}
|
|
|
|
|
: ${depsBuildTarget=} ${depsBuildTargetPropagated=}
|
|
|
|
|
: ${depsHostHost=} ${depsHostHostPropagated=}
|
|
|
|
|
: ${buildInputs=} ${propagatedBuildInputs=} ${defaultBuildInputs=}
|
|
|
|
|
: ${depsTargetTarget=} ${depsTargetTargetPropagated=}
|
|
|
|
|
|
|
|
|
|
for pkg in $depsBuildBuild $depsBuildBuildPropagated; do
|
|
|
|
|
findInputs "$pkg" -1 -1
|
|
|
|
|
done
|
|
|
|
|
for pkg in $nativeBuildInputs $propagatedNativeBuildInputs; do
|
|
|
|
|
findInputs "$pkg" -1 0
|
|
|
|
|
done
|
|
|
|
|
for pkg in $depsBuildTarget $depsBuildTargetPropagated; do
|
|
|
|
|
findInputs "$pkg" -1 1
|
|
|
|
|
done
|
|
|
|
|
for pkg in $depsHostHost $depsHostHostPropagated; do
|
|
|
|
|
findInputs "$pkg" 0 0
|
|
|
|
|
done
|
|
|
|
|
for pkg in $buildInputs $propagatedBuildInputs ; do
|
|
|
|
|
findInputs "$pkg" 0 1
|
|
|
|
|
done
|
|
|
|
|
for pkg in $depsTargetTarget $depsTargetTargetPropagated; do
|
|
|
|
|
findInputs "$pkg" 1 1
|
|
|
|
|
done
|
|
|
|
|
# Default inputs must be processed last
|
|
|
|
|
for pkg in $defaultNativeBuildInputs; do
|
|
|
|
|
findInputs "$pkg" -1 0
|
|
|
|
|
done
|
|
|
|
|
for pkg in $defaultBuildInputs; do
|
|
|
|
|
findInputs "$pkg" 0 1
|
|
|
|
|
done
|
|
|
|
|
|
2017-11-08 19:43:28 +01:00
|
|
|
|
# Add package to the future PATH and run setup hooks
|
|
|
|
|
activatePackage() {
|
|
|
|
|
local pkg="$1"
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local -r hostOffset="$2"
|
|
|
|
|
local -r targetOffset="$3"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
|
|
|
|
|
# Sanity check
|
2021-08-17 16:02:11 +02:00
|
|
|
|
(( hostOffset <= targetOffset )) || exit -1
|
2017-11-08 19:43:28 +01:00
|
|
|
|
|
2015-06-15 11:24:55 +02:00
|
|
|
|
if [ -f "$pkg" ]; then
|
|
|
|
|
source "$pkg"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
2007-11-17 15:34:27 +01:00
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Only dependencies whose host platform is guaranteed to match the
|
|
|
|
|
# build platform are included here. That would be `depsBuild*`,
|
2017-08-28 17:33:08 +02:00
|
|
|
|
# and legacy `nativeBuildInputs`, in general. If we aren't cross
|
|
|
|
|
# compiling, however, everything can be put on the PATH. To ease
|
2021-07-19 07:49:47 +02:00
|
|
|
|
# the transition, we do include everything in that case.
|
2017-08-28 17:33:08 +02:00
|
|
|
|
#
|
|
|
|
|
# TODO(@Ericson2314): Don't special-case native compilation
|
2020-11-11 16:26:06 +01:00
|
|
|
|
if [[ -z "${strictDeps-}" || "$hostOffset" -le -1 ]]; then
|
2017-07-11 22:04:14 +02:00
|
|
|
|
addToSearchPath _PATH "$pkg/bin"
|
2020-11-13 01:12:37 +01:00
|
|
|
|
fi
|
|
|
|
|
|
2021-08-17 16:02:11 +02:00
|
|
|
|
if (( hostOffset <= -1 )); then
|
2020-11-11 16:26:06 +01:00
|
|
|
|
addToSearchPath _XDG_DATA_DIRS "$pkg/share"
|
2016-02-28 01:13:15 +01:00
|
|
|
|
fi
|
|
|
|
|
|
2018-07-23 05:07:25 +02:00
|
|
|
|
if [[ "$hostOffset" -eq 0 && -d "$pkg/bin" ]]; then
|
2019-03-03 02:02:45 +01:00
|
|
|
|
addToSearchPath _HOST_PATH "$pkg/bin"
|
2018-07-23 05:07:25 +02:00
|
|
|
|
fi
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
if [[ -f "$pkg/nix-support/setup-hook" ]]; then
|
2015-06-15 11:24:55 +02:00
|
|
|
|
source "$pkg/nix-support/setup-hook"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
_activatePkgs() {
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local hostOffset targetOffset
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local pkg
|
|
|
|
|
|
|
|
|
|
for hostOffset in "${allPlatOffsets[@]}"; do
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local pkgsVar="${pkgAccumVarVars[hostOffset + 1]}"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
for targetOffset in "${allPlatOffsets[@]}"; do
|
2021-08-17 16:02:11 +02:00
|
|
|
|
(( hostOffset <= targetOffset )) || continue
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local pkgsRef="${pkgsVar}[$targetOffset - $hostOffset]"
|
|
|
|
|
local pkgsSlice="${!pkgsRef}[@]"
|
|
|
|
|
for pkg in ${!pkgsSlice+"${!pkgsSlice}"}; do
|
|
|
|
|
activatePackage "$pkg" "$hostOffset" "$targetOffset"
|
|
|
|
|
done
|
|
|
|
|
done
|
2017-11-08 19:43:28 +01:00
|
|
|
|
done
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
}
|
2017-11-17 19:26:21 +01:00
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Run the package setup hooks and build _PATH
|
|
|
|
|
_activatePkgs
|
2012-01-19 16:56:17 +01:00
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
# Set the relevant environment variables to point to the build inputs
|
|
|
|
|
# found above.
|
2017-07-06 23:19:53 +02:00
|
|
|
|
#
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# These `depOffset`s, beyond indexing the arrays, also tell the env
|
|
|
|
|
# hook what sort of dependency (ignoring propagatedness) is being
|
|
|
|
|
# passed to the env hook. In a real language, we'd append a closure
|
|
|
|
|
# with this information to the relevant env hook array, but bash
|
|
|
|
|
# doesn't have closures, so it's easier to just pass this in.
|
|
|
|
|
_addToEnv() {
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local depHostOffset depTargetOffset
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local pkg
|
|
|
|
|
|
|
|
|
|
for depHostOffset in "${allPlatOffsets[@]}"; do
|
2021-08-17 16:02:11 +02:00
|
|
|
|
local hookVar="${pkgHookVarVars[depHostOffset + 1]}"
|
|
|
|
|
local pkgsVar="${pkgAccumVarVars[depHostOffset + 1]}"
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
for depTargetOffset in "${allPlatOffsets[@]}"; do
|
2021-08-17 16:02:11 +02:00
|
|
|
|
(( depHostOffset <= depTargetOffset )) || continue
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local hookRef="${hookVar}[$depTargetOffset - $depHostOffset]"
|
2018-05-13 17:31:24 +02:00
|
|
|
|
if [[ -z "${strictDeps-}" ]]; then
|
2018-10-31 20:26:54 +01:00
|
|
|
|
|
|
|
|
|
# Keep track of which packages we have visited before.
|
|
|
|
|
local visitedPkgs=""
|
|
|
|
|
|
2017-08-28 17:33:08 +02:00
|
|
|
|
# Apply environment hooks to all packages during native
|
|
|
|
|
# compilation to ease the transition.
|
|
|
|
|
#
|
|
|
|
|
# TODO(@Ericson2314): Don't special-case native compilation
|
|
|
|
|
for pkg in \
|
2021-07-19 05:11:05 +02:00
|
|
|
|
"${pkgsBuildBuild[@]}" \
|
|
|
|
|
"${pkgsBuildHost[@]}" \
|
|
|
|
|
"${pkgsBuildTarget[@]}" \
|
|
|
|
|
"${pkgsHostHost[@]}" \
|
|
|
|
|
"${pkgsHostTarget[@]}" \
|
|
|
|
|
"${pkgsTargetTarget[@]}"
|
2017-08-28 17:33:08 +02:00
|
|
|
|
do
|
2018-10-31 20:26:54 +01:00
|
|
|
|
if [[ "$visitedPkgs" = *"$pkg"* ]]; then
|
|
|
|
|
continue
|
|
|
|
|
fi
|
2017-08-28 17:33:08 +02:00
|
|
|
|
runHook "${!hookRef}" "$pkg"
|
2018-10-31 20:26:54 +01:00
|
|
|
|
visitedPkgs+=" $pkg"
|
2017-08-28 17:33:08 +02:00
|
|
|
|
done
|
|
|
|
|
else
|
|
|
|
|
local pkgsRef="${pkgsVar}[$depTargetOffset - $depHostOffset]"
|
|
|
|
|
local pkgsSlice="${!pkgsRef}[@]"
|
|
|
|
|
for pkg in ${!pkgsSlice+"${!pkgsSlice}"}; do
|
|
|
|
|
runHook "${!hookRef}" "$pkg"
|
|
|
|
|
done
|
|
|
|
|
fi
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
done
|
|
|
|
|
done
|
2009-11-18 19:16:35 +01:00
|
|
|
|
}
|
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Run the package-specific hooks set by the setup-hook scripts.
|
|
|
|
|
_addToEnv
|
2009-11-18 19:16:35 +01:00
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2019-09-27 00:47:38 +02:00
|
|
|
|
# Unset setup-specific declared variables
|
|
|
|
|
unset allPlatOffsets
|
|
|
|
|
unset pkgBuildAccumVars pkgHostAccumVars pkgTargetAccumVars pkgAccumVarVars
|
|
|
|
|
unset pkgBuildHookVars pkgHostHookVars pkgTargetHookVars pkgHookVarVars
|
2019-11-05 22:30:40 +01:00
|
|
|
|
unset propagatedDepFilesVars
|
2019-09-27 00:47:38 +02:00
|
|
|
|
|
|
|
|
|
|
2014-08-24 19:05:56 +02:00
|
|
|
|
_addRpathPrefix "$out"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Set the TZ (timezone) environment variable, otherwise commands like
|
|
|
|
|
# `date' will complain (e.g., `Tue Mar 9 10:01:47 Local time zone must
|
|
|
|
|
# be set--see zic manual page 2004').
|
|
|
|
|
export TZ=UTC
|
|
|
|
|
|
|
|
|
|
|
2006-12-28 22:12:44 +01:00
|
|
|
|
# Set the prefix. This is generally $out, but it can be overriden,
|
|
|
|
|
# for instance if we just want to perform a test build/install to a
|
|
|
|
|
# temporary location and write a build report to $out.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${prefix:-}" ]; then
|
2017-07-16 18:10:52 +02:00
|
|
|
|
prefix="$out";
|
2006-12-28 22:12:44 +01:00
|
|
|
|
fi
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ "${useTempPrefix:-}" = 1 ]; then
|
2006-12-28 22:12:44 +01:00
|
|
|
|
prefix="$NIX_BUILD_TOP/tmp_prefix";
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
PATH="${_PATH-}${_PATH:+${PATH:+:}}$PATH"
|
2019-03-03 02:02:45 +01:00
|
|
|
|
HOST_PATH="${_HOST_PATH-}${_HOST_PATH:+${HOST_PATH:+:}}$HOST_PATH"
|
2020-11-13 01:17:35 +01:00
|
|
|
|
export XDG_DATA_DIRS="${_XDG_DATA_DIRS-}${_XDG_DATA_DIRS:+${XDG_DATA_DIRS:+:}}${XDG_DATA_DIRS-}"
|
2017-09-20 01:10:49 +02:00
|
|
|
|
if (( "${NIX_DEBUG:-0}" >= 1 )); then
|
2008-02-21 00:02:41 +01:00
|
|
|
|
echo "final path: $PATH"
|
2019-03-03 02:02:45 +01:00
|
|
|
|
echo "final host path: $HOST_PATH"
|
2020-11-11 16:26:06 +01:00
|
|
|
|
echo "final data dirs: $XDG_DATA_DIRS"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
|
2019-03-03 02:02:45 +01:00
|
|
|
|
unset _PATH
|
|
|
|
|
unset _HOST_PATH
|
2020-11-11 16:26:06 +01:00
|
|
|
|
unset _XDG_DATA_DIRS
|
2019-03-03 02:02:45 +01:00
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2009-01-19 21:31:02 +01:00
|
|
|
|
# Make GNU Make produce nested output.
|
|
|
|
|
export NIX_INDENT_MAKE=1
|
|
|
|
|
|
|
|
|
|
|
2010-06-23 16:34:59 +02:00
|
|
|
|
# Normalize the NIX_BUILD_CORES variable. The value might be 0, which
|
|
|
|
|
# means that we're supposed to try and auto-detect the number of
|
|
|
|
|
# available CPU cores at run-time.
|
|
|
|
|
|
2021-09-06 05:13:43 +02:00
|
|
|
|
NIX_BUILD_CORES="${NIX_BUILD_CORES:-1}"
|
|
|
|
|
if ((NIX_BUILD_CORES <= 0)); then
|
|
|
|
|
guess=$(nproc 2>/dev/null || true)
|
|
|
|
|
((NIX_BUILD_CORES = guess <= 0 ? 1 : guess))
|
2010-06-23 16:34:59 +02:00
|
|
|
|
fi
|
|
|
|
|
export NIX_BUILD_CORES
|
|
|
|
|
|
|
|
|
|
|
2019-05-09 08:42:07 +02:00
|
|
|
|
# Prevent SSL libraries from using certificates in /etc/ssl, unless set explicitly.
|
2019-05-09 09:49:42 +02:00
|
|
|
|
# Leave it in impure shells for convenience.
|
2021-08-19 16:23:58 +02:00
|
|
|
|
if [[ -z "${NIX_SSL_CERT_FILE:-}" && "${IN_NIX_SHELL:-}" != "impure" ]]; then
|
2019-05-09 08:42:07 +02:00
|
|
|
|
export NIX_SSL_CERT_FILE=/no-cert-file.crt
|
|
|
|
|
fi
|
|
|
|
|
# Another variant left for compatibility.
|
2021-08-19 16:23:58 +02:00
|
|
|
|
if [[ -z "${SSL_CERT_FILE:-}" && "${IN_NIX_SHELL:-}" != "impure" ]]; then
|
2016-02-25 11:53:03 +01:00
|
|
|
|
export SSL_CERT_FILE=/no-cert-file.crt
|
|
|
|
|
fi
|
2016-02-03 13:59:10 +01:00
|
|
|
|
|
|
|
|
|
|
2006-12-27 19:14:57 +01:00
|
|
|
|
######################################################################
|
|
|
|
|
# Textual substitution functions.
|
|
|
|
|
|
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
substituteStream() {
|
|
|
|
|
local var=$1
|
2018-02-23 14:12:53 +01:00
|
|
|
|
local description=$2
|
|
|
|
|
shift 2
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
2017-07-12 17:56:43 +02:00
|
|
|
|
while (( "$#" )); do
|
|
|
|
|
case "$1" in
|
|
|
|
|
--replace)
|
2017-07-16 18:10:52 +02:00
|
|
|
|
pattern="$2"
|
|
|
|
|
replacement="$3"
|
2017-07-12 17:56:43 +02:00
|
|
|
|
shift 3
|
2018-02-23 14:12:53 +01:00
|
|
|
|
local savedvar
|
|
|
|
|
savedvar="${!var}"
|
|
|
|
|
eval "$var"'=${'"$var"'//"$pattern"/"$replacement"}'
|
|
|
|
|
if [ "$pattern" != "$replacement" ]; then
|
|
|
|
|
if [ "${!var}" == "$savedvar" ]; then
|
|
|
|
|
echo "substituteStream(): WARNING: pattern '$pattern' doesn't match anything in $description" >&2
|
|
|
|
|
fi
|
|
|
|
|
fi
|
2017-07-12 17:56:43 +02:00
|
|
|
|
;;
|
|
|
|
|
|
|
|
|
|
--subst-var)
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local varName="$2"
|
2017-07-12 17:56:43 +02:00
|
|
|
|
shift 2
|
|
|
|
|
# check if the used nix attribute name is a valid bash name
|
2017-07-16 18:10:52 +02:00
|
|
|
|
if ! [[ "$varName" =~ ^[a-zA-Z_][a-zA-Z0-9_]*$ ]]; then
|
2018-05-06 21:58:03 +02:00
|
|
|
|
echo "substituteStream(): ERROR: substitution variables must be valid Bash names, \"$varName\" isn't." >&2
|
2017-08-31 16:20:51 +02:00
|
|
|
|
return 1
|
2017-07-12 17:56:43 +02:00
|
|
|
|
fi
|
2018-07-08 17:59:57 +02:00
|
|
|
|
if [ -z ${!varName+x} ]; then
|
|
|
|
|
echo "substituteStream(): ERROR: variable \$$varName is unset" >&2
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
2017-07-16 18:10:52 +02:00
|
|
|
|
pattern="@$varName@"
|
|
|
|
|
replacement="${!varName}"
|
2018-02-23 14:12:53 +01:00
|
|
|
|
eval "$var"'=${'"$var"'//"$pattern"/"$replacement"}'
|
2017-07-12 17:56:43 +02:00
|
|
|
|
;;
|
|
|
|
|
|
|
|
|
|
--subst-var-by)
|
2017-07-16 18:10:52 +02:00
|
|
|
|
pattern="@$2@"
|
|
|
|
|
replacement="$3"
|
2018-02-23 14:12:53 +01:00
|
|
|
|
eval "$var"'=${'"$var"'//"$pattern"/"$replacement"}'
|
2017-07-12 17:56:43 +02:00
|
|
|
|
shift 3
|
|
|
|
|
;;
|
|
|
|
|
|
|
|
|
|
*)
|
2018-05-06 21:58:03 +02:00
|
|
|
|
echo "substituteStream(): ERROR: Invalid command line argument: $1" >&2
|
2017-07-12 17:56:43 +02:00
|
|
|
|
return 1
|
|
|
|
|
;;
|
|
|
|
|
esac
|
2006-12-27 19:14:57 +01:00
|
|
|
|
done
|
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
printf "%s" "${!var}"
|
2006-12-27 19:14:57 +01:00
|
|
|
|
}
|
|
|
|
|
|
2021-08-03 04:07:58 +02:00
|
|
|
|
# put the content of a file in a variable
|
|
|
|
|
# fail loudly if provided with a binary (containing null bytes)
|
2018-05-06 21:58:03 +02:00
|
|
|
|
consumeEntire() {
|
|
|
|
|
# read returns non-0 on EOF, so we want read to fail
|
2021-08-03 04:07:58 +02:00
|
|
|
|
if IFS='' read -r -d '' $1 ; then
|
2018-05-06 21:58:03 +02:00
|
|
|
|
echo "consumeEntire(): ERROR: Input null bytes, won't process" >&2
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
2006-12-27 19:14:57 +01:00
|
|
|
|
}
|
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
substitute() {
|
|
|
|
|
local input="$1"
|
|
|
|
|
local output="$2"
|
|
|
|
|
shift 2
|
|
|
|
|
|
|
|
|
|
if [ ! -f "$input" ]; then
|
|
|
|
|
echo "substitute(): ERROR: file '$input' does not exist" >&2
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
local content
|
|
|
|
|
consumeEntire content < "$input"
|
|
|
|
|
|
|
|
|
|
if [ -e "$output" ]; then chmod +w "$output"; fi
|
2018-02-23 14:12:53 +01:00
|
|
|
|
substituteStream content "file '$input'" "$@" > "$output"
|
2018-05-06 21:58:03 +02:00
|
|
|
|
}
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
|
|
|
|
substituteInPlace() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local fileName="$1"
|
2006-12-27 19:14:57 +01:00
|
|
|
|
shift
|
|
|
|
|
substitute "$fileName" "$fileName" "$@"
|
|
|
|
|
}
|
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
_allFlags() {
|
|
|
|
|
for varName in $(awk 'BEGIN { for (v in ENVIRON) if (v ~ /^[a-z][a-zA-Z0-9_]*$/) print v }'); do
|
|
|
|
|
if (( "${NIX_DEBUG:-0}" >= 1 )); then
|
|
|
|
|
printf "@%s@ -> %q\n" "${varName}" "${!varName}"
|
|
|
|
|
fi
|
|
|
|
|
args+=("--subst-var" "$varName")
|
|
|
|
|
done
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
substituteAllStream() {
|
|
|
|
|
local -a args=()
|
|
|
|
|
_allFlags
|
|
|
|
|
|
2018-02-23 14:12:53 +01:00
|
|
|
|
substituteStream "$1" "$2" "${args[@]}"
|
2018-05-06 21:58:03 +02:00
|
|
|
|
}
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
2017-08-31 16:20:51 +02:00
|
|
|
|
# Substitute all environment variables that start with a lowercase character and
|
|
|
|
|
# are valid Bash names.
|
2006-12-27 19:14:57 +01:00
|
|
|
|
substituteAll() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local input="$1"
|
|
|
|
|
local output="$2"
|
2007-11-17 15:34:27 +01:00
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
local -a args=()
|
|
|
|
|
_allFlags
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
2016-04-29 11:22:47 +02:00
|
|
|
|
substitute "$input" "$output" "${args[@]}"
|
2007-11-17 15:34:27 +01:00
|
|
|
|
}
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
|
|
|
|
|
2011-07-28 22:28:37 +02:00
|
|
|
|
substituteAllInPlace() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local fileName="$1"
|
2011-07-28 22:28:37 +02:00
|
|
|
|
shift
|
|
|
|
|
substituteAll "$fileName" "$fileName" "$@"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
######################################################################
|
|
|
|
|
# What follows is the generic builder.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# This function is useful for debugging broken Nix builds. It dumps
|
|
|
|
|
# all environment variables to a file `env-vars' in the build
|
|
|
|
|
# directory. If the build fails and the `-K' option is used, you can
|
|
|
|
|
# then go to the build directory and source in `env-vars' to reproduce
|
|
|
|
|
# the environment used for building.
|
|
|
|
|
dumpVars() {
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ "${noDumpEnvVars:-0}" != 1 ]; then
|
2021-01-05 21:42:18 +01:00
|
|
|
|
export 2>/dev/null >| "$NIX_BUILD_TOP/env-vars" || true
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2016-10-12 22:29:38 +02:00
|
|
|
|
# Utility function: echo the base name of the given path, with the
|
2006-08-07 15:31:18 +02:00
|
|
|
|
# prefix `HASH-' removed, if present.
|
|
|
|
|
stripHash() {
|
2019-08-06 06:27:21 +02:00
|
|
|
|
local strippedName casematchOpt=0
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# On separate line for `set -e`
|
2019-08-06 06:27:21 +02:00
|
|
|
|
strippedName="$(basename -- "$1")"
|
|
|
|
|
shopt -q nocasematch && casematchOpt=1
|
|
|
|
|
shopt -u nocasematch
|
|
|
|
|
if [[ "$strippedName" =~ ^[a-z0-9]{32}- ]]; then
|
|
|
|
|
echo "${strippedName:33}"
|
2016-10-12 22:29:38 +02:00
|
|
|
|
else
|
|
|
|
|
echo "$strippedName"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
2019-08-06 06:27:21 +02:00
|
|
|
|
if (( casematchOpt )); then shopt -s nocasematch; fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2014-07-08 13:47:09 +02:00
|
|
|
|
unpackCmdHooks+=(_defaultUnpack)
|
2014-06-30 13:48:29 +02:00
|
|
|
|
_defaultUnpack() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local fn="$1"
|
2014-07-08 14:14:28 +02:00
|
|
|
|
|
|
|
|
|
if [ -d "$fn" ]; then
|
2014-06-30 13:21:30 +02:00
|
|
|
|
|
2016-01-26 16:21:43 +01:00
|
|
|
|
# We can't preserve hardlinks because they may have been
|
|
|
|
|
# introduced by store optimization, which might break things
|
|
|
|
|
# in the build.
|
2018-01-25 06:58:57 +01:00
|
|
|
|
cp -pr --reflink=auto -- "$fn" "$(stripHash "$fn")"
|
2014-06-30 13:21:30 +02:00
|
|
|
|
|
|
|
|
|
else
|
|
|
|
|
|
2014-07-08 14:14:28 +02:00
|
|
|
|
case "$fn" in
|
2018-07-30 16:44:35 +02:00
|
|
|
|
*.tar.xz | *.tar.lzma | *.txz)
|
2014-06-30 13:21:30 +02:00
|
|
|
|
# Don't rely on tar knowing about .xz.
|
2014-07-08 14:14:28 +02:00
|
|
|
|
xz -d < "$fn" | tar xf -
|
2014-06-30 13:21:30 +02:00
|
|
|
|
;;
|
2018-07-30 16:44:35 +02:00
|
|
|
|
*.tar | *.tar.* | *.tgz | *.tbz2 | *.tbz)
|
2014-06-30 13:21:30 +02:00
|
|
|
|
# GNU tar can automatically select the decompression method
|
|
|
|
|
# (info "(tar) gzip").
|
2014-07-08 14:14:28 +02:00
|
|
|
|
tar xf "$fn"
|
2014-06-30 13:21:30 +02:00
|
|
|
|
;;
|
|
|
|
|
*)
|
2014-06-30 13:48:29 +02:00
|
|
|
|
return 1
|
2014-06-30 13:21:30 +02:00
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
|
|
|
|
|
fi
|
2014-06-30 13:48:29 +02:00
|
|
|
|
}
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2014-06-30 13:48:29 +02:00
|
|
|
|
|
|
|
|
|
unpackFile() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
curSrc="$1"
|
2014-06-30 13:48:29 +02:00
|
|
|
|
header "unpacking source archive $curSrc" 3
|
2014-07-08 14:14:28 +02:00
|
|
|
|
if ! runOneHook unpackCmd "$curSrc"; then
|
2014-06-30 13:48:29 +02:00
|
|
|
|
echo "do not know how to unpack source archive $curSrc"
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
unpackPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preUnpack
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${srcs:-}" ]; then
|
|
|
|
|
if [ -z "${src:-}" ]; then
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2016
|
2006-08-07 15:31:18 +02:00
|
|
|
|
echo 'variable $src or $srcs should point to the source'
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
2017-07-16 18:10:52 +02:00
|
|
|
|
srcs="$src"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
# To determine the source directory created by unpacking the
|
|
|
|
|
# source archives, we record the contents of the current
|
|
|
|
|
# directory, then look below which directory got added. Yeah,
|
|
|
|
|
# it's rather hacky.
|
|
|
|
|
local dirsBefore=""
|
|
|
|
|
for i in *; do
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ -d "$i" ]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
dirsBefore="$dirsBefore $i "
|
|
|
|
|
fi
|
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
# Unpack all source archives.
|
|
|
|
|
for i in $srcs; do
|
2017-07-12 02:23:06 +02:00
|
|
|
|
unpackFile "$i"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
# Find the source directory.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
|
|
|
|
|
# set to empty if unset
|
|
|
|
|
: ${sourceRoot=}
|
|
|
|
|
|
|
|
|
|
if [ -n "${setSourceRoot:-}" ]; then
|
2014-06-30 13:48:29 +02:00
|
|
|
|
runOneHook setSourceRoot
|
2012-01-19 17:14:09 +01:00
|
|
|
|
elif [ -z "$sourceRoot" ]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
for i in *; do
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ -d "$i" ]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
case $dirsBefore in
|
|
|
|
|
*\ $i\ *)
|
|
|
|
|
;;
|
|
|
|
|
*)
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ -n "$sourceRoot" ]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
echo "unpacker produced multiple directories"
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
2017-07-16 18:10:52 +02:00
|
|
|
|
sourceRoot="$i"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
fi
|
|
|
|
|
done
|
|
|
|
|
fi
|
|
|
|
|
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ -z "$sourceRoot" ]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
echo "unpacker appears to have produced no directories"
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
echo "source root is $sourceRoot"
|
|
|
|
|
|
|
|
|
|
# By default, add write permission to the sources. This is often
|
|
|
|
|
# necessary when sources have been copied from other store
|
|
|
|
|
# locations.
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ "${dontMakeSourcesWritable:-0}" != 1 ]; then
|
2018-02-15 17:50:24 +01:00
|
|
|
|
chmod -R u+w -- "$sourceRoot"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
* Hook variables in the generic builder are now executed using eval.
This has a major advantage: you can write hooks directly in Nix
expressions. For instance, rather than write a builder like this:
source $stdenv/setup
postInstall=postInstall
postInstall() {
ln -sf gzip $out/bin/gunzip
ln -sf gzip $out/bin/zcat
}
genericBuild
(the gzip builder), you can just add this attribute to the
derivation:
postInstall = "ln -sf gzip $out/bin/gunzip; ln -sf gzip $out/bin/zcat";
and so a separate build script becomes unnecessary. This should
allow us to get rid of most builders in Nixpkgs.
* Allow configure and make arguments to contain whitespace.
Previously, you could say, for instance
configureFlags="CFLAGS=-O0"
but not
configureFlags="CFLAGS=-O0 -g"
since the `-g' would be interpreted as a separate argument to
configure. Now you can say
configureFlagsArray=("CFLAGS=-O0 -g")
or similarly
configureFlagsArray=("CFLAGS=-O0 -g" "LDFLAGS=-L/foo -L/bar")
which does the right thing. Idem for makeFlags, installFlags,
checkFlags and distFlags.
Unfortunately you can't pass arrays to Bash through the environment,
so you can't put the array above in a Nix expression, e.g.,
configureFlagsArray = ["CFLAGS=-O0 -g"];
since it would just be flattened to a since string. However, you
can use the inline hooks described above:
preConfigure = "configureFlagsArray=(\"CFLAGS=-O0 -g\")";
svn path=/nixpkgs/trunk/; revision=6863
2006-10-27 00:20:25 +02:00
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postUnpack
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
patchPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook prePatch
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
for i in ${patches:-}; do
|
2006-08-07 15:31:18 +02:00
|
|
|
|
header "applying patch $i" 3
|
2006-12-27 19:14:57 +01:00
|
|
|
|
local uncompress=cat
|
2014-10-09 21:41:56 +02:00
|
|
|
|
case "$i" in
|
2006-12-27 19:14:57 +01:00
|
|
|
|
*.gz)
|
2007-12-03 18:55:41 +01:00
|
|
|
|
uncompress="gzip -d"
|
2006-12-27 19:14:57 +01:00
|
|
|
|
;;
|
|
|
|
|
*.bz2)
|
2007-12-03 18:55:41 +01:00
|
|
|
|
uncompress="bzip2 -d"
|
2006-12-27 19:14:57 +01:00
|
|
|
|
;;
|
2013-08-07 15:45:21 +02:00
|
|
|
|
*.xz)
|
|
|
|
|
uncompress="xz -d"
|
|
|
|
|
;;
|
2009-12-18 12:26:36 +01:00
|
|
|
|
*.lzma)
|
|
|
|
|
uncompress="lzma -d"
|
|
|
|
|
;;
|
2006-12-27 19:14:57 +01:00
|
|
|
|
esac
|
2013-06-27 16:34:31 +02:00
|
|
|
|
# "2>&1" is a hack to make patch fail if the decompressor fails (nonexistent patch, etc.)
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2014-10-09 21:41:56 +02:00
|
|
|
|
$uncompress < "$i" 2>&1 | patch ${patchFlags:--p1}
|
2006-08-07 15:31:18 +02:00
|
|
|
|
done
|
2008-03-18 12:03:35 +01:00
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postPatch
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixLibtool() {
|
2008-06-11 16:08:01 +02:00
|
|
|
|
sed -i -e 's^eval sys_lib_.*search_path=.*^^' "$1"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
configurePhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preConfigure
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# set to empty if unset
|
|
|
|
|
: ${configureScript=}
|
|
|
|
|
: ${configureFlags=}
|
|
|
|
|
|
2017-07-16 18:10:52 +02:00
|
|
|
|
if [[ -z "$configureScript" && -x ./configure ]]; then
|
2006-08-07 15:31:18 +02:00
|
|
|
|
configureScript=./configure
|
|
|
|
|
fi
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${dontFixLibtool:-}" ]; then
|
2021-07-24 23:56:01 +02:00
|
|
|
|
export lt_cv_deplibs_check_method="${lt_cv_deplibs_check_method-pass_all}"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
local i
|
|
|
|
|
find . -iname "ltmain.sh" -print0 | while IFS='' read -r -d '' i; do
|
2006-08-07 15:31:18 +02:00
|
|
|
|
echo "fixing libtool script $i"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
fixLibtool "$i"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
done
|
|
|
|
|
fi
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [[ -z "${dontAddPrefix:-}" && -n "$prefix" ]]; then
|
2007-11-17 15:34:27 +01:00
|
|
|
|
configureFlags="${prefixKey:---prefix=}$prefix $configureFlags"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
|
2021-07-19 08:24:39 +02:00
|
|
|
|
if [[ -f "$configureScript" ]]; then
|
|
|
|
|
# Add --disable-dependency-tracking to speed up some builds.
|
|
|
|
|
if [ -z "${dontAddDisableDepTrack:-}" ]; then
|
|
|
|
|
if grep -q dependency-tracking "$configureScript"; then
|
|
|
|
|
configureFlags="--disable-dependency-tracking $configureFlags"
|
|
|
|
|
fi
|
2008-02-13 19:27:19 +01:00
|
|
|
|
fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2021-07-19 08:24:39 +02:00
|
|
|
|
# By default, disable static builds.
|
|
|
|
|
if [ -z "${dontDisableStatic:-}" ]; then
|
|
|
|
|
if grep -q enable-static "$configureScript"; then
|
|
|
|
|
configureFlags="--disable-static $configureFlags"
|
|
|
|
|
fi
|
2009-04-22 00:40:12 +02:00
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
|
2015-12-30 11:11:33 +01:00
|
|
|
|
if [ -n "$configureScript" ]; then
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# Old bash empty array hack
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local flagsArray=(
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$configureFlags "${configureFlagsArray[@]}"
|
2017-08-09 07:20:56 +02:00
|
|
|
|
)
|
2017-07-13 22:31:39 +02:00
|
|
|
|
echoCmd 'configure flags' "${flagsArray[@]}"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
|
|
|
|
$configureScript "${flagsArray[@]}"
|
|
|
|
|
unset flagsArray
|
2015-12-30 11:11:33 +01:00
|
|
|
|
else
|
|
|
|
|
echo "no configure script, doing nothing"
|
|
|
|
|
fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postConfigure
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
buildPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preBuild
|
2007-11-17 15:34:27 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# set to empty if unset
|
|
|
|
|
: ${makeFlags=}
|
|
|
|
|
|
2018-03-15 01:00:01 +01:00
|
|
|
|
if [[ -z "$makeFlags" && -z "${makefile:-}" && ! ( -e Makefile || -e makefile || -e GNUmakefile ) ]]; then
|
2008-02-21 00:02:41 +01:00
|
|
|
|
echo "no Makefile, doing nothing"
|
2015-12-30 11:11:33 +01:00
|
|
|
|
else
|
2018-03-15 01:00:04 +01:00
|
|
|
|
foundMakefile=1
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# Old bash empty array hack
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local flagsArray=(
|
|
|
|
|
${enableParallelBuilding:+-j${NIX_BUILD_CORES} -l${NIX_BUILD_CORES}}
|
2019-01-27 03:09:37 +01:00
|
|
|
|
SHELL=$SHELL
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$makeFlags "${makeFlagsArray[@]}"
|
|
|
|
|
$buildFlags "${buildFlagsArray[@]}"
|
2017-08-09 07:20:56 +02:00
|
|
|
|
)
|
2017-07-12 02:23:06 +02:00
|
|
|
|
|
2017-07-13 22:31:39 +02:00
|
|
|
|
echoCmd 'build flags' "${flagsArray[@]}"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
make ${makefile:+-f $makefile} "${flagsArray[@]}"
|
|
|
|
|
unset flagsArray
|
2008-02-21 00:02:41 +01:00
|
|
|
|
fi
|
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postBuild
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
checkPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preCheck
|
2008-03-18 12:03:35 +01:00
|
|
|
|
|
2018-03-15 01:00:04 +01:00
|
|
|
|
if [[ -z "${foundMakefile:-}" ]]; then
|
2020-11-07 11:52:59 +01:00
|
|
|
|
echo "no Makefile or custom checkPhase, doing nothing"
|
2018-03-15 01:00:04 +01:00
|
|
|
|
runHook postCheck
|
|
|
|
|
return
|
|
|
|
|
fi
|
2017-07-12 02:23:06 +02:00
|
|
|
|
|
2018-03-15 01:00:04 +01:00
|
|
|
|
if [[ -z "${checkTarget:-}" ]]; then
|
|
|
|
|
#TODO(@oxij): should flagsArray influence make -n?
|
|
|
|
|
if make -n ${makefile:+-f $makefile} check >/dev/null 2>&1; then
|
|
|
|
|
checkTarget=check
|
|
|
|
|
elif make -n ${makefile:+-f $makefile} test >/dev/null 2>&1; then
|
|
|
|
|
checkTarget=test
|
|
|
|
|
fi
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
if [[ -z "${checkTarget:-}" ]]; then
|
|
|
|
|
echo "no check/test target in ${makefile:-Makefile}, doing nothing"
|
|
|
|
|
else
|
|
|
|
|
# Old bash empty array hack
|
|
|
|
|
# shellcheck disable=SC2086
|
|
|
|
|
local flagsArray=(
|
2018-09-05 03:08:14 +02:00
|
|
|
|
${enableParallelChecking:+-j${NIX_BUILD_CORES} -l${NIX_BUILD_CORES}}
|
2019-01-27 03:09:37 +01:00
|
|
|
|
SHELL=$SHELL
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$makeFlags "${makeFlagsArray[@]}"
|
|
|
|
|
${checkFlags:-VERBOSE=y} "${checkFlagsArray[@]}"
|
2018-03-15 01:00:04 +01:00
|
|
|
|
${checkTarget}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
echoCmd 'check flags' "${flagsArray[@]}"
|
|
|
|
|
make ${makefile:+-f $makefile} "${flagsArray[@]}"
|
|
|
|
|
|
|
|
|
|
unset flagsArray
|
|
|
|
|
fi
|
2008-03-18 12:03:35 +01:00
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postCheck
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
installPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preInstall
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2014-08-25 15:30:46 +02:00
|
|
|
|
if [ -n "$prefix" ]; then
|
|
|
|
|
mkdir -p "$prefix"
|
|
|
|
|
fi
|
2006-12-27 19:14:57 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# Old bash empty array hack
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local flagsArray=(
|
2019-01-27 03:09:37 +01:00
|
|
|
|
SHELL=$SHELL
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$makeFlags "${makeFlagsArray[@]}"
|
|
|
|
|
$installFlags "${installFlagsArray[@]}"
|
2018-03-15 01:00:02 +01:00
|
|
|
|
${installTargets:-install}
|
2017-08-09 07:20:56 +02:00
|
|
|
|
)
|
2017-07-12 02:23:06 +02:00
|
|
|
|
|
2017-07-13 22:31:39 +02:00
|
|
|
|
echoCmd 'install flags' "${flagsArray[@]}"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
make ${makefile:+-f $makefile} "${flagsArray[@]}"
|
|
|
|
|
unset flagsArray
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postInstall
|
2006-12-27 19:14:57 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2014-06-25 16:47:58 +02:00
|
|
|
|
# The fixup phase performs generic, package-independent stuff, like
|
|
|
|
|
# stripping binaries, running patchelf and setting
|
|
|
|
|
# propagated-build-inputs.
|
2008-02-21 00:02:41 +01:00
|
|
|
|
fixupPhase() {
|
2014-01-14 14:13:31 +01:00
|
|
|
|
# Make sure everything is writable so "strip" et al. work.
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
local output
|
2014-06-25 16:47:58 +02:00
|
|
|
|
for output in $outputs; do
|
2014-07-08 14:15:44 +02:00
|
|
|
|
if [ -e "${!output}" ]; then chmod -R u+w "${!output}"; fi
|
2014-06-25 16:47:58 +02:00
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
runHook preFixup
|
2014-01-14 14:13:31 +01:00
|
|
|
|
|
2014-06-25 16:47:58 +02:00
|
|
|
|
# Apply fixup to each output.
|
|
|
|
|
local output
|
|
|
|
|
for output in $outputs; do
|
2017-07-16 18:10:52 +02:00
|
|
|
|
prefix="${!output}" runHook fixupOutput
|
2014-06-25 16:47:58 +02:00
|
|
|
|
done
|
|
|
|
|
|
2015-04-18 15:46:00 +02:00
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
# Propagate dependencies & setup hook into the development output.
|
|
|
|
|
declare -ra flatVars=(
|
|
|
|
|
# Build
|
|
|
|
|
depsBuildBuildPropagated
|
|
|
|
|
propagatedNativeBuildInputs
|
|
|
|
|
depsBuildTargetPropagated
|
|
|
|
|
# Host
|
|
|
|
|
depsHostHostPropagated
|
|
|
|
|
propagatedBuildInputs
|
|
|
|
|
# Target
|
|
|
|
|
depsTargetTargetPropagated
|
|
|
|
|
)
|
|
|
|
|
declare -ra flatFiles=(
|
|
|
|
|
"${propagatedBuildDepFiles[@]}"
|
|
|
|
|
"${propagatedHostDepFiles[@]}"
|
|
|
|
|
"${propagatedTargetDepFiles[@]}"
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
local propagatedInputsIndex
|
|
|
|
|
for propagatedInputsIndex in "${!flatVars[@]}"; do
|
|
|
|
|
local propagatedInputsSlice="${flatVars[$propagatedInputsIndex]}[@]"
|
|
|
|
|
local propagatedInputsFile="${flatFiles[$propagatedInputsIndex]}"
|
2014-08-24 18:37:23 +02:00
|
|
|
|
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
[[ "${!propagatedInputsSlice}" ]] || continue
|
2014-06-25 16:47:58 +02:00
|
|
|
|
|
2017-11-17 19:26:21 +01:00
|
|
|
|
mkdir -p "${!outputDev}/nix-support"
|
|
|
|
|
# shellcheck disable=SC2086
|
stdenv: Fix handling of dependencies and hooks
4 far-reaching changes: Smaller PATH, New vars, different propagation
logic, and different hook logic
Smaller PATH
------------
`buildInputs` no longer go on the PATH at build time, as they cannot be
run when cross compiling and we don't want to special case. Simply make
a `nativeBuildInput` too if one needs them on the PATH. Fixes #21191.
Many new depedendency variables
-------------------------------
See the stdenv chapter of the nixpkgs manual. I pulled out the existing
documentation of dependency specification into a new section, and added
language for these two (and their propagated equivalents) along side
the others'.
More complex propagation logic
------------------------------
Before a propagated*XXX*Input always acted as if it was specified
directly as a *XXX*Input downstream. That's simple enough, but violates
the intended roles of each sort of dep, which has functional and not
just stylistic consequences.
The new algorithm is detailed in the manual, and ensures everything
ends up in the right place. I tried to give both an informal and formal
description, but I suspect in practice it will not make much sense
until one tries cross compiling, after which it will immediately make
sense as the only sane option.
Simplified hook logic
---------------------
Rather than `envHook` and `crossEnvHook`, whose behavior differs
depending on whether we are cross compiling or not, there is now one
hook per sort (or rather non-propagated and propagated pair of sorts)
of dependency. These new hooks have the same meaning regardless of
cross compilation. See the setup hook section of stdenv chapter of the
Nixpkgs manual for more details.
2017-09-11 18:20:20 +02:00
|
|
|
|
printWords ${!propagatedInputsSlice} > "${!outputDev}/nix-support/$propagatedInputsFile"
|
|
|
|
|
done
|
2014-06-25 16:47:58 +02:00
|
|
|
|
|
2017-11-17 19:26:21 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${setupHook:-}" ]; then
|
2015-04-18 15:46:00 +02:00
|
|
|
|
mkdir -p "${!outputDev}/nix-support"
|
|
|
|
|
substituteAll "$setupHook" "${!outputDev}/nix-support/setup-hook"
|
2014-06-25 16:47:58 +02:00
|
|
|
|
fi
|
|
|
|
|
|
2018-05-06 21:58:03 +02:00
|
|
|
|
# TODO(@Ericson2314): Remove after https://github.com/NixOS/nixpkgs/pull/31414
|
|
|
|
|
if [ -n "${setupHooks:-}" ]; then
|
|
|
|
|
mkdir -p "${!outputDev}/nix-support"
|
|
|
|
|
local hook
|
|
|
|
|
for hook in $setupHooks; do
|
|
|
|
|
local content
|
|
|
|
|
consumeEntire content < "$hook"
|
2018-02-23 14:12:53 +01:00
|
|
|
|
substituteAllStream content "file '$hook'" >> "${!outputDev}/nix-support/setup-hook"
|
2018-05-06 21:58:03 +02:00
|
|
|
|
unset -v content
|
|
|
|
|
done
|
|
|
|
|
unset -v hook
|
|
|
|
|
fi
|
|
|
|
|
|
2015-04-18 15:46:00 +02:00
|
|
|
|
# Propagate user-env packages into the output with binaries, TODO?
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${propagatedUserEnvPkgs:-}" ]; then
|
2015-04-18 15:46:00 +02:00
|
|
|
|
mkdir -p "${!outputBin}/nix-support"
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-07-26 00:48:47 +02:00
|
|
|
|
printWords $propagatedUserEnvPkgs > "${!outputBin}/nix-support/propagated-user-env-packages"
|
2014-06-25 16:47:58 +02:00
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
runHook postFixup
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2012-05-01 23:00:30 +02:00
|
|
|
|
installCheckPhase() {
|
|
|
|
|
runHook preInstallCheck
|
|
|
|
|
|
2018-03-15 01:00:04 +01:00
|
|
|
|
if [[ -z "${foundMakefile:-}" ]]; then
|
2020-11-07 11:52:59 +01:00
|
|
|
|
echo "no Makefile or custom installCheckPhase, doing nothing"
|
2018-03-15 01:00:04 +01:00
|
|
|
|
#TODO(@oxij): should flagsArray influence make -n?
|
|
|
|
|
elif [[ -z "${installCheckTarget:-}" ]] \
|
|
|
|
|
&& ! make -n ${makefile:+-f $makefile} ${installCheckTarget:-installcheck} >/dev/null 2>&1; then
|
|
|
|
|
echo "no installcheck target in ${makefile:-Makefile}, doing nothing"
|
|
|
|
|
else
|
|
|
|
|
# Old bash empty array hack
|
|
|
|
|
# shellcheck disable=SC2086
|
|
|
|
|
local flagsArray=(
|
2018-09-05 03:08:14 +02:00
|
|
|
|
${enableParallelChecking:+-j${NIX_BUILD_CORES} -l${NIX_BUILD_CORES}}
|
2019-01-27 03:09:37 +01:00
|
|
|
|
SHELL=$SHELL
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$makeFlags "${makeFlagsArray[@]}"
|
|
|
|
|
$installCheckFlags "${installCheckFlagsArray[@]}"
|
2018-03-15 01:00:04 +01:00
|
|
|
|
${installCheckTarget:-installcheck}
|
|
|
|
|
)
|
2017-07-12 02:23:06 +02:00
|
|
|
|
|
2018-03-15 01:00:04 +01:00
|
|
|
|
echoCmd 'installcheck flags' "${flagsArray[@]}"
|
|
|
|
|
make ${makefile:+-f $makefile} "${flagsArray[@]}"
|
|
|
|
|
unset flagsArray
|
|
|
|
|
fi
|
2012-05-01 23:00:30 +02:00
|
|
|
|
|
|
|
|
|
runHook postInstallCheck
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
distPhase() {
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook preDist
|
2007-11-17 15:34:27 +01:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
# Old bash empty array hack
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-08-09 07:20:56 +02:00
|
|
|
|
local flagsArray=(
|
2021-07-19 05:11:05 +02:00
|
|
|
|
$distFlags "${distFlagsArray[@]}" ${distTarget:-dist}
|
2017-08-09 07:20:56 +02:00
|
|
|
|
)
|
2017-07-12 02:23:06 +02:00
|
|
|
|
|
|
|
|
|
echo 'dist flags: %q' "${flagsArray[@]}"
|
|
|
|
|
make ${makefile:+-f $makefile} "${flagsArray[@]}"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ "${dontCopyDist:-0}" != 1 ]; then
|
2012-01-18 21:16:00 +01:00
|
|
|
|
mkdir -p "$out/tarballs"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
|
|
|
|
|
# Note: don't quote $tarballs, since we explicitly permit
|
|
|
|
|
# wildcards in there.
|
2017-07-12 02:23:06 +02:00
|
|
|
|
# shellcheck disable=SC2086
|
2017-07-16 18:10:52 +02:00
|
|
|
|
cp -pvd ${tarballs:-*.tar.gz} "$out/tarballs"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
fi
|
|
|
|
|
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postDist
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
showPhaseHeader() {
|
2017-07-16 18:10:52 +02:00
|
|
|
|
local phase="$1"
|
|
|
|
|
case "$phase" in
|
2008-02-21 00:02:41 +01:00
|
|
|
|
unpackPhase) header "unpacking sources";;
|
|
|
|
|
patchPhase) header "patching sources";;
|
|
|
|
|
configurePhase) header "configuring";;
|
|
|
|
|
buildPhase) header "building";;
|
|
|
|
|
checkPhase) header "running tests";;
|
|
|
|
|
installPhase) header "installing";;
|
|
|
|
|
fixupPhase) header "post-installation fixup";;
|
2012-05-01 23:00:30 +02:00
|
|
|
|
installCheckPhase) header "running install tests";;
|
2008-02-21 00:02:41 +01:00
|
|
|
|
*) header "$phase";;
|
|
|
|
|
esac
|
2006-08-07 15:31:18 +02:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
genericBuild() {
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -f "${buildCommandPath:-}" ]; then
|
|
|
|
|
source "$buildCommandPath"
|
2016-05-29 15:25:09 +02:00
|
|
|
|
return
|
|
|
|
|
fi
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -n "${buildCommand:-}" ]; then
|
2006-12-27 19:14:57 +01:00
|
|
|
|
eval "$buildCommand"
|
|
|
|
|
return
|
|
|
|
|
fi
|
|
|
|
|
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [ -z "${phases:-}" ]; then
|
|
|
|
|
phases="${prePhases:-} unpackPhase patchPhase ${preConfigurePhases:-} \
|
|
|
|
|
configurePhase ${preBuildPhases:-} buildPhase checkPhase \
|
|
|
|
|
${preInstallPhases:-} installPhase ${preFixupPhases:-} fixupPhase installCheckPhase \
|
|
|
|
|
${preDistPhases:-} distPhase ${postPhases:-}";
|
2008-02-21 00:02:41 +01:00
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
for curPhase in $phases; do
|
2019-06-19 17:37:51 +02:00
|
|
|
|
if [[ "$curPhase" = unpackPhase && -n "${dontUnpack:-}" ]]; then continue; fi
|
2020-04-12 13:03:27 +02:00
|
|
|
|
if [[ "$curPhase" = patchPhase && -n "${dontPatch:-}" ]]; then continue; fi
|
2019-06-19 15:00:14 +02:00
|
|
|
|
if [[ "$curPhase" = configurePhase && -n "${dontConfigure:-}" ]]; then continue; fi
|
2017-08-09 07:20:56 +02:00
|
|
|
|
if [[ "$curPhase" = buildPhase && -n "${dontBuild:-}" ]]; then continue; fi
|
|
|
|
|
if [[ "$curPhase" = checkPhase && -z "${doCheck:-}" ]]; then continue; fi
|
|
|
|
|
if [[ "$curPhase" = installPhase && -n "${dontInstall:-}" ]]; then continue; fi
|
|
|
|
|
if [[ "$curPhase" = fixupPhase && -n "${dontFixup:-}" ]]; then continue; fi
|
|
|
|
|
if [[ "$curPhase" = installCheckPhase && -z "${doInstallCheck:-}" ]]; then continue; fi
|
|
|
|
|
if [[ "$curPhase" = distPhase && -z "${doDist:-}" ]]; then continue; fi
|
|
|
|
|
|
2017-09-07 22:24:27 +02:00
|
|
|
|
if [[ -n $NIX_LOG_FD ]]; then
|
|
|
|
|
echo "@nix { \"action\": \"setPhase\", \"phase\": \"$curPhase\" }" >&$NIX_LOG_FD
|
|
|
|
|
fi
|
|
|
|
|
|
2008-02-21 00:02:41 +01:00
|
|
|
|
showPhaseHeader "$curPhase"
|
2006-08-07 15:31:18 +02:00
|
|
|
|
dumpVars
|
2012-12-28 16:41:56 +01:00
|
|
|
|
|
2014-01-07 09:43:39 +01:00
|
|
|
|
# Evaluate the variable named $curPhase if it exists, otherwise the
|
|
|
|
|
# function named $curPhase.
|
|
|
|
|
eval "${!curPhase:-$curPhase}"
|
2008-02-21 00:02:41 +01:00
|
|
|
|
|
2012-01-19 17:14:09 +01:00
|
|
|
|
if [ "$curPhase" = unpackPhase ]; then
|
2008-02-21 00:02:41 +01:00
|
|
|
|
cd "${sourceRoot:-.}"
|
|
|
|
|
fi
|
2006-08-07 15:31:18 +02:00
|
|
|
|
done
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2014-01-07 09:48:23 +01:00
|
|
|
|
# Execute the post-hooks.
|
2009-02-01 22:28:02 +01:00
|
|
|
|
runHook postHook
|
2008-02-21 00:02:41 +01:00
|
|
|
|
|
|
|
|
|
|
2012-12-28 16:36:09 +01:00
|
|
|
|
# Execute the global user hook (defined through the Nixpkgs
|
|
|
|
|
# configuration option ‘stdenv.userHook’). This can be used to set
|
|
|
|
|
# global compiler optimisation flags, for instance.
|
|
|
|
|
runHook userHook
|
|
|
|
|
|
|
|
|
|
|
2006-08-07 15:31:18 +02:00
|
|
|
|
dumpVars
|
2017-08-09 07:20:56 +02:00
|
|
|
|
|
|
|
|
|
# Disable nounset for nix-shell.
|
|
|
|
|
set +u
|