2020-11-07 19:39:21 +00:00
|
|
|
# $NetBSD: varname-dot-parsefile.mk,v 1.5 2020/10/24 08:50:17 rillig Exp $
|
2020-09-05 16:11:04 +00:00
|
|
|
#
|
2020-11-07 19:39:21 +00:00
|
|
|
# Tests for the special .PARSEFILE variable, which contains the basename part
|
|
|
|
# of the file that is currently parsed.
|
2020-09-05 16:11:04 +00:00
|
|
|
|
2020-11-07 19:39:21 +00:00
|
|
|
.if ${.PARSEFILE} != "varname-dot-parsefile.mk"
|
|
|
|
. error
|
|
|
|
.endif
|
|
|
|
|
|
|
|
# During parsing, it is possible to undefine .PARSEFILE.
|
|
|
|
# Not that anyone would ever want to do this, but there's code in parse.c,
|
|
|
|
# function PrintLocation, that explicitly handles this situation.
|
|
|
|
.if !defined(.PARSEFILE)
|
|
|
|
. error
|
|
|
|
.endif
|
|
|
|
.undef .PARSEFILE
|
|
|
|
.if defined(.PARSEFILE)
|
|
|
|
. error
|
|
|
|
.endif
|
|
|
|
|
|
|
|
# The variable .PARSEFILE is indirectly used by the .info directive,
|
|
|
|
# via PrintLocation.
|
|
|
|
.info At this point, .PARSEFILE is undefined.
|
|
|
|
|
|
|
|
# There is absolutely no point in faking the location of the file that is
|
|
|
|
# being parsed. Technically, it's possible though, but only if the file
|
|
|
|
# being parsed is a relative pathname. See PrintLocation for details.
|
|
|
|
.PARSEFILE= fake-parsefile
|
|
|
|
.info The location can be faked in some cases.
|
|
|
|
|
|
|
|
# After including another file, .PARSEFILE is reset.
|
|
|
|
.include "/dev/null"
|
|
|
|
.info The location is no longer fake.
|
2020-09-05 16:11:04 +00:00
|
|
|
|
|
|
|
all:
|
2020-11-07 19:39:21 +00:00
|
|
|
@echo At run time, .PARSEFILE is ${.PARSEFILE:Uundefined}.
|