149

For variable assignment in Make, I see := and = operator. What's the difference between them?

Joseph Quinsey
  • 9,185
  • 10
  • 53
  • 75
prosseek
  • 169,389
  • 197
  • 542
  • 840
  • 7
    possible duplicate of [Makefile variable assignment](http://stackoverflow.com/questions/448910/makefile-variable-assignment) – eldarerathis Feb 02 '11 at 20:40
  • 2
    Possible duplicate of [What is the difference between the GNU Makefile variable assignments =, ?=, := and +=?](https://stackoverflow.com/questions/448910/what-is-the-difference-between-the-gnu-makefile-variable-assignments-a) – Ludovic Kuty Oct 24 '18 at 04:19

6 Answers6

126

Simple assignment :=

A simple assignment expression is evaluated only once, at the very first occurrence. For example, if CC :=${GCC} ${FLAGS} during the first encounter is evaluated to gcc -W then each time ${CC} occurs it will be replaced with gcc -W.

Recursive assignment =

A Recursive assignment expression is evaluated everytime the variable is encountered in the code. For example, a statement like CC = ${GCC} {FLAGS} will be evaluated only when an action like ${CC} file.c is executed. However, if the variable GCC is reassigned i.e GCC=c++ then the ${CC} will be converted to c++ -W after the reassignment.

Conditional assignment ?=

Conditional assignment assigns a value to a variable only if it does not have a value

Appending +=

Assume that CC = gcc then the appending operator is used like CC += -w
then CC now has the value gcc -W

For more check out these tutorials

Czechnology
  • 14,723
  • 10
  • 60
  • 87
Amjad
  • 2,390
  • 2
  • 15
  • 18
  • 4
    "A simple assignment expression is evaluated only once, at the very first occurrence": to be clear, the expansion/evaluation is done when the variable is defined, not the first time it is used. – Michael Burr Apr 22 '20 at 15:32
111

This is described in the GNU Make documentation, in the section titled 6.2 The Two Flavors of Variables .

In short, variables defined with := are expanded once, but variables defined with = are expanded whenever they are used.

Greg Hewgill
  • 890,778
  • 177
  • 1,125
  • 1,260
  • 5
    So would it be correct to say that := is more efficient? Or is efficiency not really a factor with Makefiles? – Ungeheuer Apr 27 '17 at 14:45
  • 3
    @Ungeheuer That's not an issue because process calling (the `make`'s main job) has much larger overhead than such internal variable resolving. – Kirill Bulygin May 15 '17 at 10:51
28

For me, the best way to see it in practice is during this Makefile snippet:

Simple assignment

XX := $(shell date) // date will be executed once
tt:
    @echo $(XX)
    $(shell sleep 2)
    @echo $(XX)

Running

make tt

Will produce:

sex 22 jan 2021 14:56:08 -03
sex 22 jan 2021 14:56:08 -03

( Same value )

Expanded assignment

XX = $(shell date) // date will be executed every time you use XX
tt:
    @echo $(XX)
    $(shell sleep 2)
    @echo $(XX)

Running

make tt

Will produce:

sex 22 jan 2021 14:56:08 -03
sex 22 jan 2021 14:56:10 -03

Different values

xn.
  • 15,358
  • 2
  • 27
  • 33
Edgard Leal
  • 2,225
  • 24
  • 30
12

From http://www.gnu.org/software/make/manual/make.html#Flavors:

= defines a recursively-expanded variable. := defines a simply-expanded variable.

Oliver Charlesworth
  • 260,367
  • 30
  • 546
  • 667
2

This is an old question but this example helps me understand the difference whenever I forget.

Running make with the following Makefile will instantly exit:

a = $(shell sleep 3)

Running make with the following Makefile will sleep for 3 seconds, and then exit:

a := $(shell sleep 3)

In the former Makefile, a is not evaluated until it's used elsewhere in the Makefile, while in the latter a is evaluated immediately even though it's not used.

Andrey Kaipov
  • 505
  • 6
  • 13
1

Recursive assignment = is evaluated everytime it is used, but not in the order of when it is encountered among the recipe commands, but rather before running any recipe command.

Based on the following example:

default: target1 target2

target1 target2:
    @echo "Running at:           `gdate +%s.%N`"
    @echo "Simple assignment:    $(SIMPLE_ASSIGNMENT)"
    @echo "Recursive assignment: $(RECURSIVE_ASSIGNMENT)"
    sleep 1
    @echo "Running at:           `gdate +%s.%N`"
    @echo "Simple assignment:    $(SIMPLE_ASSIGNMENT)"
    @echo "Recursive assignment: $(RECURSIVE_ASSIGNMENT)"
    @echo


SIMPLE_ASSIGNMENT := $(shell gdate +%s.%N)
RECURSIVE_ASSIGNMENT = $(shell gdate +%s.%N)

Outputs:

❯ make
Running at:           1645056840.980488000
Simple assignment:    1645056840.949181000
Recursive assignment: 1645056840.958590000
sleep 1
Running at:           1645056842.008998000
Simple assignment:    1645056840.949181000
Recursive assignment: 1645056840.969616000

Running at:           1645056842.047367000
Simple assignment:    1645056840.949181000
Recursive assignment: 1645056842.027600000
sleep 1
Running at:           1645056843.076696000
Simple assignment:    1645056840.949181000
Recursive assignment: 1645056842.035901000
Utsav Munendra
  • 59
  • 5