zephyr/tests/crypto/test_cbc_mode/Makefile

BOARD ?= qemu_x86
MDEF_FILE = prj.mdef
KERNEL_TYPE = micro
CONF_FILE = prj.conf

include $(ZEPHYR_BASE)/Makefile.inc
Use BOARD instead of PLATFORM_CONFIG Change-Id: I14db0087cd705df0db8a911071bc3949b5c79314 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-12-14 04:00:31 +08:00			`BOARD ?= qemu_x86`
Add initial import of TinyCrypt crypto library and tests Change-Id: I89b8db6925385dd02e95e0401bc42f32543e0daf Signed-off-by: Constanza Heath <constanza.m.heath@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-08-22 07:16:58 +08:00			`MDEF_FILE = prj.mdef`
			`KERNEL_TYPE = micro`
samples: get rid of obsolete usage of ARCH variable Using ARCH variable to select different configurations for the different architectures is misleading and conflicts with the variable ARCH being used by the build system. The variable is not needed, it is application specific and an application can be built without the need to specify ARCH on the command line. This is yet another item specific to samples and test cases that wrongfully being used and documented for every application. We need to use another variable and just make it clear it is specific to samples and how they are written. One possible solution is to have a script that gets the architecture based on the board being used. Attachments Jira: ZEP-238 Change-Id: Ieccbc087a41858fb96fb361c0aaa04705e968a4e Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-05-12 08:22:01 +08:00			`CONF_FILE = prj.conf`
Add initial import of TinyCrypt crypto library and tests Change-Id: I89b8db6925385dd02e95e0401bc42f32543e0daf Signed-off-by: Constanza Heath <constanza.m.heath@intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-08-22 07:16:58 +08:00
			`include $(ZEPHYR_BASE)/Makefile.inc`