RIOT/boards/wsn430-common/Makefile.include

## the cpu to build for
export CPU = msp430fxyz
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)msp430_common/startup.o
export FLASHER = mspdebug
ifeq ($(strip $(PORT)),)
    export PORT = /dev/ttyUSB0
endif
export FFLAGS = -d $(PORT) -j uif "prog $(HEXFILE)"

export INCLUDES += -I$(RIOTBOARD)/wsn430-common/include
export OFLAGS = -O ihex

export UNDEF += $(BINDIR)msp430_common/startup.o
added support for board wsn430-v1_3b 2013-05-25 12:34:18 +02:00			`## the cpu to build for`
cpu: msp430: renamed msp430x16x to msp430fxyz 2014-12-01 17:32:29 +01:00			`export CPU = msp430fxyz`
added support for board wsn430-v1_3b 2013-05-25 12:34:18 +02:00			`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)`
added support for board wsn430-v1_3b 2013-05-25 12:34:18 +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`
make: don't overwrite LINKFLAGS Fix the boards' Makefiles were a potentially set LINKFLAGS variable were overwritten. 2014-10-17 22:39:45 +02:00			`export LINKFLAGS += -mmcu=$(MCU) -lgcc $(BINDIR)msp430_common/startup.o`
added support for board wsn430-v1_3b 2013-05-25 12:34:18 +02:00			`export FLASHER = mspdebug`
			`ifeq ($(strip $(PORT)),)`
			`export PORT = /dev/ttyUSB0`
			`endif`
			`export FFLAGS = -d $(PORT) -j uif "prog $(HEXFILE)"`

further Makefile cleanup 2013-12-24 14:50:26 +01:00			`export INCLUDES += -I$(RIOTBOARD)/wsn430-common/include`
added objcopy flags to makefiles for all platforms 2013-10-11 15:07:53 +02:00			`export OFLAGS = -O ihex`
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
			`export UNDEF += $(BINDIR)msp430_common/startup.o`