riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

avr: Use TARGET_ARCH instead of custom toolchain specification

Browse Source
This commit is contained in:
Joakim Nohlgård 2016-03-21 09:25:42 +01:00
parent cad5f08b56
commit d0033a5d20
2 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
boards/arduino-mega2560/Makefile.include
View File

@ -1,15 +1,6 @@
# define the cpu used by the arduino mega2560 board # define the cpu used by the arduino mega2560 board
export CPU = atmega2560 export CPU = atmega2560
# define tools used for building the project
export PREFIX = avr-
export CC = $(PREFIX)gcc
export CXX = $(PREFIX)c++
export AR = $(PREFIX)ar
export AS = $(PREFIX)as
export LINK = $(PREFIX)gcc
export SIZE = $(PREFIX)size
export OBJCOPY = $(PREFIX)objcopy
export TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm export TERMPROG = $(RIOTBASE)/dist/tools/pyterm/pyterm
export TERMFLAGS = -b 9600 -p $(PORT) export TERMFLAGS = -b 9600 -p $(PORT)

2
cpu/atmega_common/Makefile.include
View File

@ -1,3 +1,5 @@
# Target architecture for the build. Use avr if you are unsure.
export TARGET_ARCH ?= avr
# include module specific includes # include module specific includes
export INCLUDES += -I$(RIOTCPU)/atmega_common/include -isystem$(RIOTCPU)/atmega_common/avr-libc-extra export INCLUDES += -I$(RIOTCPU)/atmega_common/include -isystem$(RIOTCPU)/atmega_common/avr-libc-extra