mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
3f59eefbaf
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 ```
34 lines
1010 B
Makefile
34 lines
1010 B
Makefile
## the cpu to build for
|
|
export CPU = msp430x16x
|
|
export MCU = msp430f1612
|
|
|
|
# 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
|
|
TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm.py
|
|
export HEXFILE = $(BINDIR)$(PROJECT).hex
|
|
|
|
export FLASHER ?= mspdebug
|
|
export PORT ?= /dev/ttyUSB0
|
|
export PROGRAMMER ?= olimex
|
|
export FFLAGS += -j $(PROGRAMMER)
|
|
ifeq ($(strip $(PROGRAMMER)),uif)
|
|
export FFLAGS += -d $(PORT)
|
|
endif
|
|
|
|
export FFLAGS += "prog $(HEXFILE)"
|
|
|
|
export USEMODULE += msp430_common
|
|
export INCLUDES += -I$(RIOTCPU)/msp430-common/include/ -I$(RIOTBOARD)/msb-430-common/include -I$(RIOTBOARD)/msb-430-common/drivers/include
|
|
export OFLAGS = -O ihex
|
|
|
|
export UNDEF += $(BINDIR)msp430_common/startup.o
|