RIOT/tests/build_system_cflags_spaces/Makefile

include ../Makefile.tests_common
CFLAGS += -DSUPER_STRING='"I love sentences with spaces"'

include $(RIOTBASE)/Makefile.include

# Changing this value should trigger a rebuild even if defined after
# Makefile.include
CONFIGURATION_VALUE ?= 0
CFLAGS += -DDEFINED_AFTER_MAKEFILE_INCLUDE=$(CONFIGURATION_VALUE)
# Exported to be available in the automated test
test: export CONFIGURATION_VALUE ?=
tests: don't define APPLICATION in application Makefile The right way is to include the common test Makefile where the application is automatically defined. 2019-11-01 14:07:35 +01:00			`include ../Makefile.tests_common`
tests/build_system_cflags_spaces: test CFLAGS macros handling This tests passing CFLAGS with spaces to an application and also that even if the CFLAGS are defined after Makefile.include, they trigger a rebuild when modified. This includes an example how to pass macros with spaces to a docker build. The test as both an automated part for the CFLAGS with spaces, and a manual part for the two other features. 2019-09-18 11:34:27 +02:00			`CFLAGS += -DSUPER_STRING='"I love sentences with spaces"'`

			`include $(RIOTBASE)/Makefile.include`

			`# Changing this value should trigger a rebuild even if defined after`
			`# Makefile.include`
			`CONFIGURATION_VALUE ?= 0`
			`CFLAGS += -DDEFINED_AFTER_MAKEFILE_INCLUDE=$(CONFIGURATION_VALUE)`
			`# Exported to be available in the automated test`
			`test: export CONFIGURATION_VALUE ?=`