-
Notifications
You must be signed in to change notification settings - Fork 0
The Make Build System
RIOT uses a recursive Makefile system. The starting point for these structure is typically the Makefile within the application's Makefile. Among other variables it sets the path to the RIOT repository as $RIOTBASE
.
Usually, the last thing in an application's Makefile is to include the Makefile.include
from $RIOTBASE
.
In the simplest case a module just needs to provide a Makefile that does nothing more than including Makefile.base
from $RIOTBASE
. If the name of your module does not match the name of the directory containing the code, one has to set the variable MODULE
as well. E.g. by adding MODULE = FOOBAR
as the first line of the module's Makefile.
All RIOT specific variables used in the Make build system are listed and briefly explained in Makefile.vars.
RIOT - The friendly Operating System for the Internet of Things
Homepage | [GitHub] (https://github.com/RIOT-OS/) | Developers Mailing List | Users Mailing List | Twitter @RIOT_OS
- Family: ARM
- Board: Airfy Beacon
- Board: Arduino Due
- Board: CC2538DK
- Board: HikoB Fox
- Board: IoT LAB M3
- Board: LimiFrog-v1
- Board: mbed_lpc1768
- Board: MSB-IoT
- Board: MSBA2
- Board: Nucleo-L1
- Board: Nucleo-F334
- Board: Nucleo-F303
- Board: Nucleo-F091
- Board: Mulle
- Board: OpenMote
- Board: PCA1000x (nRF51822 Development Kit)
- Board: Phytec phyWAVE-KW22
- Board: RFduino
- Board: Samr21 xpro
- Board: Spark Core
- Board: STM32F0discovery
- Board: STM32F3discovery
- Board: STM32F4discovery
- Board: UDOO
- Board: yunjia-nrf51822
- Family: ATmega
- Board: Arduino Mega2560
- Family: MSP430
- Board: MSB-430H
- Board: TelosB
- Board: WSN430
- Board: Zolertia Z1
- Board: eZ430-Chronos
- Family: native
- Board: native
- Family: x86
- Board: Intel Galileo