freebsd-dev/contrib/bmake/unit-tests/var-recursive.mk
2022-02-05 12:26:16 -08:00

62 lines
1.6 KiB
Makefile

# $NetBSD: var-recursive.mk,v 1.4 2022/01/29 10:21:26 rillig Exp $
#
# Tests for variable expressions that refer to themselves and thus
# cannot be evaluated.
TESTS= direct indirect conditional short target
# Since make exits immediately when it detects a recursive expression,
# the actual tests are run in sub-makes.
TEST?= # none
.if ${TEST} == ""
all:
.for test in ${TESTS}
@${.MAKE} -f ${MAKEFILE} TEST=${test} || :
.endfor
.elif ${TEST} == direct
DIRECT= ${DIRECT} # Defining a recursive variable is not yet an error.
. info still there # Therefore this line is printed.
. info ${DIRECT} # But expanding the variable is an error.
.elif ${TEST} == indirect
# The chain of variables that refer to each other may be long.
INDIRECT1= ${INDIRECT2}
INDIRECT2= ${INDIRECT1}
. info ${INDIRECT1}
.elif ${TEST} == conditional
# The variable refers to itself, but only in the branch of a condition that
# is never satisfied and is thus not evaluated.
CONDITIONAL= ${1:?ok:${CONDITIONAL}}
. info ${CONDITIONAL}
.elif ${TEST} == short
# Short variable names can be expanded using the short-hand $V notation,
# which takes a different code path in Var_Parse for parsing the variable
# name. Ensure that these are checked as well.
V= $V
. info $V
.elif ${TEST} == target
# If a recursive variable is accessed in a command of a target, the makefiles
# are not parsed anymore, so there is no location information from the
# .includes and .for directives. In such a case, use the location of the last
# command of the target to provide at least a hint to the location.
VAR= ${VAR}
target:
: OK
: ${VAR}
: OK
.else
. error Unknown test "${TEST}"
.endif
all: