RIOT/boards/telosb/Makefile.include

include $(RIOTBOARD)/$(BOARD)/Makefile.dep
## the cpu to build for
export CPU = msp430x16x
export MCU = msp430f1611

# toolchain config
export PREFIX = msp430-
export CC = $(PREFIX)gcc
export AR = $(PREFIX)ar
export CFLAGS += -Wstrict-prototypes -gdwarf-2 -Os -Wall -mmcu=$(MCU)
export ASFLAGS += -mmcu=$(MCU) --defsym $(MCU)=1 --gdwarf-2
export AS = $(PREFIX)as
export LINK = $(PREFIX)gcc
export SIZE = $(PREFIX)size
export OBJCOPY = $(PREFIX)objcopy
export LINKFLAGS = -mmcu=$(MCU) -lgcc $(BINDIR)startup.o
export TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm.py
export FLASHER = goodfet.bsl
ifeq ($(strip $(PORT)),)
    export PORT = /dev/ttyUSB0
endif
export HEXFILE = $(BINDIR)$(PROJECT).hex
export FFLAGS = --telosb -c $(PORT) -r -e -I -p $(HEXFILE)

export INCLUDES += -I$(RIOTCPU)/msp430-common/include -I$(RIOTBOARD)/$(BOARD)/include -I$(RIOTBASE)/drivers/cc2420/include -I$(RIOTBASE)/sys/net/include
export OFLAGS = -O ihex
initial commit for TelosB support 2013-08-19 18:58:45 +02:00			`include $(RIOTBOARD)/$(BOARD)/Makefile.dep`
			`## the cpu to build for`
			`export CPU = msp430x16x`
			`export MCU = msp430f1611`

			`# toolchain config`
muting compiler and binutils optionally Instead of muting all compiler and other binutils output by default, introduce a variable to make this behaviour configurable. 2014-01-03 19:00:41 +01:00			`export PREFIX = msp430-`
			`export CC = $(PREFIX)gcc`
			`export AR = $(PREFIX)ar`
Do not mandate input language An application might want to use C11 features. The user would assume that setting `CFLAGS=-std=gnu11` in the Makefile would work. It does not since the board's Makefile.include shadows the `-std` flag. This patch removes the `-std=gnu99` from the various Makefile.includes, and sets the flag in the common Makefile.include of RIOT instead. If an `-std` flag was provided by an earlier Makefile (the application, the board, or the CPU [whilst only the former one should]), then no additional flag is set. It is first tested if the supplied compiler understands `-std=gnu99`, then `-std=c99`. 2014-02-12 17:32:34 +01:00			`export CFLAGS += -Wstrict-prototypes -gdwarf-2 -Os -Wall -mmcu=$(MCU)`
initial commit for TelosB support 2013-08-19 18:58:45 +02:00			`export ASFLAGS += -mmcu=$(MCU) --defsym $(MCU)=1 --gdwarf-2`
			`export AS = $(PREFIX)as`
			`export LINK = $(PREFIX)gcc`
			`export SIZE = $(PREFIX)size`
			`export OBJCOPY = $(PREFIX)objcopy`
removed superfluous slash after BINDIR 2013-12-24 13:20:25 +01:00			`export LINKFLAGS = -mmcu=$(MCU) -lgcc $(BINDIR)startup.o`
initial commit for TelosB support 2013-08-19 18:58:45 +02:00			`export TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm.py`
			`export FLASHER = goodfet.bsl`
			`ifeq ($(strip $(PORT)),)`
			`export PORT = /dev/ttyUSB0`
			`endif`
use proper variables in board Makefiles 2014-01-03 18:45:07 +01:00			`export HEXFILE = $(BINDIR)$(PROJECT).hex`
initial commit for TelosB support 2013-08-19 18:58:45 +02:00			`export FFLAGS = --telosb -c $(PORT) -r -e -I -p $(HEXFILE)`

make: couple include path and -I This is necessary if includes have to be filtered, such as in native to throw out RIOTs posix includes which interfere with system includes. 2014-02-27 08:14:33 +01:00			`export INCLUDES += -I$(RIOTCPU)/msp430-common/include -I$(RIOTBOARD)/$(BOARD)/include -I$(RIOTBASE)/drivers/cc2420/include -I$(RIOTBASE)/sys/net/include`
added OFLAGS to Makefile.include for telosb 2013-12-16 15:06:31 +01:00			`export OFLAGS = -O ihex`