RIOT/tests/mcuboot/Makefile

BOARD ?= nrf52dk

include ../Makefile.tests_common

BOARD_WHITELIST := nrf52dk

export IMAGE_VERSION = 1.1.1+1

# this test is supposed to always build the mcuboot image
ifneq ($(BUILD_IN_DOCKER),1)
# HACK: When building with docker, mcuboot target must be done only in docker
all: mcuboot
endif

include $(RIOTBASE)/Makefile.include
tests: add mcuboot test application 2017-06-13 17:35:23 +02:00			`BOARD ?= nrf52dk`

			`include ../Makefile.tests_common`

			`BOARD_WHITELIST := nrf52dk`

			`export IMAGE_VERSION = 1.1.1+1`

			`# this test is supposed to always build the mcuboot image`
tests/mcuboot: handle building 'mcuboot' in docker When using BUILD_IN_DOCKER only make 'all' execute 'mcuboot' target when inside the container. Otherwise it will execute it using your host toolchain. This is a hack and could be prevented by having a file target put in FLASHFILE. This does currently not allow flashing after building in docker as flashing should be done with `mcuboot-flash` which will not be done in docker. It would require the `FLASHFILE` fix to be done properly. 2019-02-28 17:01:52 +01:00			`ifneq ($(BUILD_IN_DOCKER),1)`
			`# HACK: When building with docker, mcuboot target must be done only in docker`
tests: add mcuboot test application 2017-06-13 17:35:23 +02:00			`all: mcuboot`
tests/mcuboot: handle building 'mcuboot' in docker When using BUILD_IN_DOCKER only make 'all' execute 'mcuboot' target when inside the container. Otherwise it will execute it using your host toolchain. This is a hack and could be prevented by having a file target put in FLASHFILE. This does currently not allow flashing after building in docker as flashing should be done with `mcuboot-flash` which will not be done in docker. It would require the `FLASHFILE` fix to be done properly. 2019-02-28 17:01:52 +01:00			`endif`
tests: add mcuboot test application 2017-06-13 17:35:23 +02:00
			`include $(RIOTBASE)/Makefile.include`