zephyr/arch/arm/Kbuild

subdir-ccflags-y +=-I$(srctree)/include/drivers
subdir-ccflags-y +=-I$(srctree)/drivers
subdir-asflags-y := ${subdir-ccflags-y}

obj-y += soc/$(SOC_NAME)/
obj-y += core/
arm: remove repeating cflags in Makefiles Do not repeat the same flags for every added platform. Define the common flags on the architecture level instead. Change-Id: I0e501d6a909892dd682b106fb2a5072434a39563 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-11-03 09:58:01 +08:00			`subdir-ccflags-y +=-I$(srctree)/include/drivers`
			`subdir-ccflags-y +=-I$(srctree)/drivers`
			`subdir-asflags-y := ${subdir-ccflags-y}`

Use SoC instead of platform. Change terminology and use SoC instead of platform. An SoC provides features and default configurations available with an SoC. A board implements the SoC and adds more features and IP block specific to the board to extend the SoC functionality such as sensors and debugging features. Change-Id: I15e8d78a6d4ecd5cfb3bc25ced9ba77e5ea1122f Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-12-17 21:54:35 +08:00			`obj-y += soc/$(SOC_NAME)/`
build: fix issue with static interrupts on ARC/ARM Static interrupts rely on a trick where the _sw_isr_table array is declared with each element in a different .gnu.linkonce section, initially pointing to the spurious IRQ handler. When drivers or apps declare their own interrupts, they override the element with their own containing the real ISR and parameter. However, this only works if the initial declaration of the _sw_isr_table array with the spurious handlers is linked last. App-specific code was being linked later than the core code, causing static interrupts declared in apps not to be installed correctly. If the _sw_isr_table is moved from SOC-specific code to core arch code, interrupts configured under soc/ should still also work. Change-Id: Iec7df47386dfbbf2956a807da27dc8aa6e01b268 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2016-01-28 06:40:45 +08:00			`obj-y += core/`