RIOT/boards/chronos/Makefile.include

## the cpu to build for
export CPU = cc430
export CPU_MODEL = cc430f6137

# flasher configuration
export OFLAGS = -O ihex
export FLASHER = mspdebug
export FFLAGS = rf2500 "prog $(HEXFILE)"

INCLUDES += -I$(RIOTBOARD)/$(BOARD)/drivers/include

USEMODULE += chronos-drivers
modified and cleaned some files to build RIOT for chronos 2013-03-30 21:37:56 +01:00			`## the cpu to build for`
			`export CPU = cc430`
boards/chronos: Makefile cleanup 2015-09-16 17:17:37 +02:00			`export CPU_MODEL = cc430f6137`
modified and cleaned some files to build RIOT for chronos 2013-03-30 21:37:56 +01:00
boards/chronos: Makefile cleanup 2015-09-16 17:17:37 +02:00			`# flasher configuration`
			`export OFLAGS = -O ihex`
modified and cleaned some files to build RIOT for chronos 2013-03-30 21:37:56 +01:00			`export FLASHER = mspdebug`
fix FFLAGS 2013-12-11 18:20:58 +01:00			`export FFLAGS = rf2500 "prog $(HEXFILE)"`
Use subfolders in bin dir Creating all object files in one directory is bound to produce name clashes. RIOT developers may take care to use unique file names, but external packages surely don't. With this change all the objects of a module (e.g. `shell`) will be created in `bin/$(BOARD)/$(MODULE)`. I compared the final linker command before and after the change. The `.o` files (e.g. `startup.o`, `syscall.o` ...) are included in the same order. Neglecting the changed path name where the `.o` files reside, the linker command stays exactly the same. A major problem could be third party boards, because the location of the `startup.o` needs to the specified now in `boards/$(BOARD)/Makefile.include`, e.g. ```Makefile export UNDEF += $(BINDIR)msp430_common/startup.o ``` 2014-02-15 12:31:43 +01:00
make: Move BOARD and CPU includes to Makefile.modules 2016-02-10 07:29:13 +01:00			`INCLUDES += -I$(RIOTBOARD)/$(BOARD)/drivers/include`
boards/chronos: Use another module name for drivers subdirectory 2016-03-08 14:19:23 +01:00
			`USEMODULE += chronos-drivers`