RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
2c1b516c8e
RIOT/sys/Makefile.include

93 lines
3.0 KiB
Makefile
Raw Normal View History

sys/auto-init: added mechanism to init network ifs
2015-04-29 21:17:07 +02:00
ifneq (,$(filter auto_init,$(USEMODULE)))
include $(RIOTBASE)/sys/auto_init/Makefile.include
endif
sys: net: Initial import of a basic MAC protocol layer
2014-07-19 18:00:21 +02:00
ifneq (,$(filter nomac,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
transport_layer: Splitting UDP and TCP Currently, the tcp and udp implementations are bound to each other in a module called *destiny*. Thus, when using only one of them then the other one gets also compiled into the binary and initialized, which results in unnecessary RAM usage and workload for the CPU. The approach in this PR defines a common module named *socket_base*, which contains functions used by the posix layer. Compiled by it's own, those functions return negative error codes, to symbolize upper layers that they are not supported. When also including the modules *udp* or *tcp* respectively, functions from *socket_base* get overwritten with the correct functionality. Defining *udp* or *tcp* in a Makefile also includes *socket_base*. Defining *pnet* in a Makefile also includes *socket_base*.
2014-07-31 17:53:46 +02:00
ifneq (,$(filter transport_layer,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
ifneq (,$(filter socket_base,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
ifneq (,$(filter tcp,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
ifneq (,$(filter udp,$(USEMODULE)))
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
sys: net: Initial import of a general interface to a network protocol
2014-07-18 17:30:26 +02:00
ifneq (,$(filter netapi,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
ifneq (,$(filter net_help,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
drivers - cc110x: Initial import of new cc110x driver
2014-09-23 01:30:37 +02:00
USEMODULE_INCLUDES += $(RIOTBASE)/drivers/cc110x
drivers - cc110x: rename cc110x to cc110x_legacy_csma
2014-10-26 22:02:18 +01:00
USEMODULE_INCLUDES += $(RIOTBASE)/drivers/cc110x_legacy_csma
drivers - cc110x_ng: rename ng driver to legacy
2014-10-19 13:47:19 +02:00
USEMODULE_INCLUDES += $(RIOTBASE)/drivers/cc110x_legacy/include
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
endif
ifneq (,$(filter net_if,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
net: Initial import of a packet wrapper for priority_queue
2014-09-05 18:21:58 +02:00
ifneq (,$(filter pktqueue,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
ifneq (,$(filter protocol_multiplex,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
ifneq (,$(filter sixlowpan,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
ifneq (,$(filter rpl,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/routing/rpl
endif
sys - nhdp: Add nhdp impl
2014-11-25 12:02:52 +01:00
ifneq (,$(filter nhdp,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/routing/nhdp
endif
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
ifneq (,$(filter ieee802154,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
net: move ping to sys/net * moved the former ping module from `sys` to `sys/net/link_layer` and renamed to l2_ping * use defaulttransceiver instead of cc110x * some refactoring
2014-05-22 23:18:51 +02:00
ifneq (,$(filter l2_ping,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
ifneq (,$(filter ccn_lite,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/ccn_lite
endif
ifneq (,$(filter ccn_lite_client,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/net/include
endif
sys:crypto: put ciphers into one module
2014-05-08 19:06:07 +02:00
ifneq (,$(filter crypto,$(USEMODULE)))
Add include paths automatocally for USEMODULES Application developers use `$(USEMODULES)` in their Makefiles to have the relevant functionally automagically added to their apps. This even does basic dependency tracking by means of `Makefile.dep`. But an important thing is missing: the automatic adding of include paths. This is inconvenient, error prone, and will hinder the RIOT core developers in future to change folder structures.
2014-02-26 23:23:15 +01:00
USEMODULE_INCLUDES += $(RIOTBASE)/include/crypto
endif
ifneq (,$(filter posix,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/posix/include
endif
ifneq (,$(filter pnet,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/posix/pnet/include
endif
ifneq (,$(filter pthread,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/posix/pthread/include
endif
msp430: provide oneway-malloc implicitly For MSP430 boards oneway-malloc is already used *if* `malloc.h` was included. The problem is that `malloc.h` is not a standard header, even though it is common. `stdlib.h` in the right place to look for `malloc()` and friends. This change removes this discrepancy. `malloc()` is just named like that, without the leading underscore. The symbols now are weak, which means that they won't override library functions if MSP's standard library will provide these functions at some point. (Unlikely, since using `malloc()` on tiny systems is less then optimal ...) Closes #1061 and #863.
2014-05-15 16:30:47 +02:00
ifneq (,$(filter oneway_malloc,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/oneway-malloc/include
endif
tests: make embUnit a normal sys module There is nothing quite special about embUnit. This PR makes it a normal sys module, so that you can use it in any application / test.
2014-11-27 22:30:14 +01:00
net: added a core implementation of a FIB
2014-11-04 08:47:57 +01:00
ifneq (,$(filter fib,$(USEMODULE)))
USEMODULE_INCLUDES += $(RIOTBASE)/sys/include/net
endif
tests: make embUnit a normal sys module There is nothing quite special about embUnit. This PR makes it a normal sys module, so that you can use it in any application / test.
2014-11-27 22:30:14 +01:00
ifneq (,$(filter embunit,$(USEMODULE)))
ifeq ($(OUTPUT),XML)
CFLAGS += -DOUTPUT=OUTPUT_XML
else ifeq ($(OUTPUT),TEXT)
CFLAGS += -DOUTPUT=OUTPUT_TEXT
else ifeq ($(OUTPUT),COMPILER)
CFLAGS += -DOUTPUT=OUTPUT_COMPILER
endif
endif
Copy Permalink