avr: Use TARGET_ARCH instead of custom toolchain specification
This commit is contained in:
parent
cad5f08b56
commit
d0033a5d20
@ -1,15 +1,6 @@
|
||||
# define the cpu used by the arduino mega2560 board
|
||||
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 TERMFLAGS = -b 9600 -p $(PORT)
|
||||
|
||||
|
||||
@ -1,3 +1,5 @@
|
||||
# Target architecture for the build. Use avr if you are unsure.
|
||||
export TARGET_ARCH ?= avr
|
||||
|
||||
# include module specific includes
|
||||
export INCLUDES += -I$(RIOTCPU)/atmega_common/include -isystem$(RIOTCPU)/atmega_common/avr-libc-extra
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user