[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #51973] variable value set by target-specific assignment not availa

From: anonymous
Subject: [bug #51973] variable value set by target-specific assignment not available to reference in multi-line variable definition
Date: Sat, 9 Sep 2017 16:53:26 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; OpenBSD amd64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Follow-up Comment #1, bug #51973 (project make):

This makefile is behaving as defined: when $(call) is used, make performs a
round of variable expansion on the value of the variable that is called.  So,
when you say

$(call EXELNK,utl1)

make expands that to

utl1:;@echo "jfh1:pt1::"

This expansion is taking place at the top-level of make parsing and not in the
context of building a target, so there are no target-specific variable
settings to use and $(OBJ1) expands to nothing.  Later, when make invokes that
recipe to build the target, it does another round of variable expansion with
the target-specific variables in place...but at that point there are no
variable references left.

In order to have it expand to what you want, you need get the $(OBJ1) variable
reference through the $(call) expansion through to the actual target building.
 To do that, double the dollar-sign:

define EXELNK
$(1):;@echo "jfh1:pt1:$$(OBJ1):"

During the expansion of the $(call), the $$ will expand to $ so that the full
rule will be

utl1:;@echo "jfh1:pt1:$(OBJ1):"

...and then when it's invoked as a recipe that target-specific variable
expansion will take place as desired.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]