Browse Source
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 ```dev/timer

14 changed files with 38 additions and 21 deletions
@ -1,3 +1,3 @@
|
||||
INCLUDES += -I$(RIOTBASE)/cpu/arm_common/include/
|
||||
|
||||
export UNDEF += $(BINDIR)syscalls.o
|
||||
export UNDEF += $(BINDIR)arm_common/syscalls.o
|
||||
|
@ -1,3 +1,3 @@
|
||||
INCLUDES += -I$(RIOTBASE)/cpu/lpc1768/include
|
||||
|
||||
export UNDEF += $(BINDIR)syscalls.o
|
||||
export UNDEF += $(BINDIR)cpu/syscalls.o
|
||||
|
@ -1,3 +1,3 @@
|
||||
INCLUDES += -I$(RIOTCPU)/lpc_common/include
|
||||
|
||||
export UNDEF += $(BINDIR)lpc_syscalls.o
|
||||
export UNDEF += $(BINDIR)lpc_common/lpc_syscalls.o
|
||||
|
Loading…
Reference in new issue