mcuboot/boot/zephyr/Makefile

subdir-ccflags-y += -DMCUBOOT_TARGET_CONFIG='"$(BOARD).h"'
subdir-ccflags-y += -I$(PROJECT)/boot/bootutil/include
subdir-ccflags-y += -I$(PROJECT)/boot/zephyr/include
subdir-ccflags-y += -I$(PROJECT)/boot/zephyr/targets

obj-y += main.o
obj-y += flash_map.o hal_flash.o os.o
obj-y += keys.o

obj-y += ../bootutil/src/
zephyr: restructure the build process to use board config files Move the board specific configurations into its own header file, which can now be created per board, once it gets tested and validated by the bootloader. Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> 2017-01-19 20:22:35 +08:00			`subdir-ccflags-y += -DMCUBOOT_TARGET_CONFIG='"$(BOARD).h"'`
zephyr: Move Zephyr build to top level The Zephyr build system does strange things if it refers to source directories above the main Makefile (generating outdir/<target>/../boot/... paths). For now, fix this by moving the Zephyr Makefile to the top-level in the tree. This shouldn't have much impact on Mynewt, as it doesn't use makefiles. 2017-01-10 01:35:50 +08:00			`subdir-ccflags-y += -I$(PROJECT)/boot/bootutil/include`
zephyr: Move code under 'boot' directory The Zephyr build systems makes some assumptions about the directory layout, and encounters problems if the necessary path contains "../..". To help this, place the zephyr directory next to the bootutil directory so that the Makefile can just refer to "../bootutil". This keeps all of the build artifacts under the proper top-level directory. 2017-01-11 00:49:47 +08:00			`subdir-ccflags-y += -I$(PROJECT)/boot/zephyr/include`
zephyr: restructure the build process to use board config files Move the board specific configurations into its own header file, which can now be created per board, once it gets tested and validated by the bootloader. Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> 2017-01-19 20:22:35 +08:00			`subdir-ccflags-y += -I$(PROJECT)/boot/zephyr/targets`
zephyr: Bring in the Zephyr build Add support for building mcuboot as a Zephyr application. This is copied from the iotboot repo with some minor reorganization to work with the mcuboot directory layout. 2017-01-07 02:16:53 +08:00
			`obj-y += main.o`
			`obj-y += flash_map.o hal_flash.o os.o`
			`obj-y += keys.o`

zephyr: Move code under 'boot' directory The Zephyr build systems makes some assumptions about the directory layout, and encounters problems if the necessary path contains "../..". To help this, place the zephyr directory next to the bootutil directory so that the Makefile can just refer to "../bootutil". This keeps all of the build artifacts under the proper top-level directory. 2017-01-11 00:49:47 +08:00			`obj-y += ../bootutil/src/`