From 5b1ce32bbced20b01be2dcea4ecca510a7194b75 Mon Sep 17 00:00:00 2001 From: "Kelvin M. Klann" Date: Tue, 6 Dec 2022 06:42:54 -0300 Subject: build: use CPPFLAGS instead of INCLUDE in compile targets With this, CFLAGS and CPPFLAGS are used when compiling and LDFLAGS when linking, just like in the built-in GNU make rules. From `make -p`: COMPILE.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c LINK.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH) LINK.o = $(CC) $(LDFLAGS) $(TARGET_ARCH) Note: It is unclear where the `INCLUDE` variable comes from; it is not documented in autoconf nor GNU make and automake (which itself is not used in this repository) only mentions `INCLUDES`: `INCLUDES` This does the same job as `AM_CPPFLAGS` (or any per-target `_CPPFLAGS` variable if it is used). It is an older name for the same functionality. This variable is deprecated; we suggest using `AM_CPPFLAGS` and per-target `_CPPFLAGS` instead. Environment: automake 1.16.5-2 and GNU make 4.4.1 on Artix Linux. See also commit 671c3f249 ("build: actually set LDFLAGS and LIBS in makefiles", 2022-11-30) / PR #5504. --- config.mk.in | 1 + 1 file changed, 1 insertion(+) (limited to 'config.mk.in') diff --git a/config.mk.in b/config.mk.in index 958efdb34..403d78e37 100644 --- a/config.mk.in +++ b/config.mk.in @@ -76,6 +76,7 @@ MANFLAGS = \ # https://www.gnu.org/software/automake/manual/1.16.5/html_node/User-Variables.html CC=@CC@ CFLAGS=@CFLAGS@ +CPPFLAGS=@CPPFLAGS@ LDFLAGS=@LDFLAGS@ # Project variables -- cgit v1.2.3-70-g09d2