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
9cf0119233
RIOT/Makefile.features

33 lines
1.1 KiB
Makefile
Raw Normal View History

build system: Restructure dependency resolution Goals: - Untangle dependency resolution and feature checking for better maintainability - Improve performance of "make info-boards-supported" Changes: - Makefile.dep - Dropped handling of default modules and recursion - Now only dependencies of the current set of used modules and pkgs are added ==> External recursion is needed to catch transient dependencies - Changed Makefile.features: - Dropped checking of provided features - Dropped populating FEATURES_USED with provided features that are required or optional - Dropped populating FEATURES_MISSING with required but not provided features - Dropped adding modules implementing used features to USE_MODULE ==> This now only populates FEATURES_PROVIDED, nothing more - Added makefiles/features_check.inc.mk: - This performs the population of FEATURES_USED and FEATURES_MISSING now - Added makefiles/features_modules.inc.mk: - This performs now the addition of modules implementing used features - Added makefiles/dependency_resolution.inc.mk: - This now performs the recursion required to catch transient dependencies - Also the feature check is performed recursively to handle also required and optional features of the transient dependencies - DEFAULT_MODULES are added repeatedly to allow it to be extended based on used features and modules ==> This allows modules to have optional dependencies, as these dependencies can be blacklisted - Use simply expanded variables instead of recursively expended variables (`foo := $(bar)` instead `foo = $(bar)`) for internal variables during feature resolution. This improves performance significantly for `make info-boards-supported`. - Reduce dependency resolution steps in `make info-boards-supported` - Globally resolve dependencies without any features (including arch) provided ==> This results in the common subset of feature requirements and modules used - But for individual boards additional modules might be used on top due to architecture specific dependencies or optional features - Boards not supporting this subset of commonly required features are not supported, so no additional dependency resolution is needed for them - For each board supporting the common set of requirements a complete dependency resolution is still needed to also catch architecture specific hacks - But this resolution is seeded with the common set of dependencies to speed this up
2020-03-19 14:06:47 +01:00
# Process provided FEATURES
Makefile.features: add doc on CPU/CPU_MODEL definition in board Describe the ongoing migration. Part of moving CPU/CPU_MODEL definition to Makefile.features to have it available before Makefile.include.
2019-05-02 17:01:20 +02:00
#
# The board/board common are responsible for defining the CPU and CPU_MODEL
# variables in their Makefile.features.
# This makes them available when setting features based on CPU_MODEL in the cpu
# Makefile.features and also during dependency resolution.
makefiles: use 'BOARDSDIR' for the boards directory in compilation Replace uses of 'RIOTBOARD' by 'BOARDSDIR' during the compilation.
2019-09-09 17:00:59 +02:00
# Transition:
# Moving 'CPU/CPU_MODEL' to Makefile.features is an ongoing work and may not
# reflect the state of all boards for the moment.
Makefile*: Allow multiple external board dirs - Add the new EXTERNAL_BOARD_DIRS variable that can contain a space separated list of folders containing external boards - Introduce $(BOARDDIR) as shortcut for $(BOARDSDIR)/$(BOARD) - Map the existing BOARDSDIR to the new approach - If BOARDSDIR is provided by the user, it will be added to EXTERNAL_BOARD_DIRS for backward compatibility. (And a warning is issued to encourage users migrating to EXTRA_BOARDS.) - BOARDSDIR is updated after the board is found to "$(BOARDDIR)/..". - Useful for `include $(BOARDSDIR)/common/external_common/Makefile.dep` - Provides backward compatibility
2020-04-14 15:23:23 +02:00
include $(BOARDDIR)/Makefile.features
Makefile.features: declare FEATURES_MISSING and make use of it Put the definition of `FEATURES_MISSING` in common and use the variable instead of duplicating code.
2019-05-03 16:19:20 +02:00
Makefile.features: assert CPU is defined by BOARD/Makefile.features CPU must now be defined by `$(RIOTBOARD)/$(BOARD)/Makefile.features` or one of its common included Makefile.features file. The cpu `Makefile.dep` file can now automatically be included when it exists.
2018-09-11 14:13:08 +02:00
# Sanity check
ifeq (,$(CPU))
$(error CPU must be defined by board / board_common Makefile.features)
Makefile.features: include CPU/Makefile.features when CPU is defined Prepare for when boards define `CPU` in `BOARD/Makefile.features`. Include '$(RIOTCPU)/$(CPU)/Makefile.features' directly when it is defined. This will allow removing the file inclusion from the `BOARD/Makefile.features`. The board must then not include it directly. Transitional change to allow migrating part by parts. Part of moving CPU/CPU_MODEL definition to Makefile.features to have it available before Makefile.include.
2019-05-02 11:49:20 +02:00
endif
Makefile.features: assert CPU is defined by BOARD/Makefile.features CPU must now be defined by `$(RIOTBOARD)/$(BOARD)/Makefile.features` or one of its common included Makefile.features file. The cpu `Makefile.dep` file can now automatically be included when it exists.
2018-09-11 14:13:08 +02:00
include $(RIOTCPU)/$(CPU)/Makefile.features
Makefile.features: provide CPU as a feature Provide the feature `cpu_$(CPU)` This allows to easily list all boards with a CPU by running FEATURES_REQUIRED=cpu_samd21 make info-boards-supported
2020-03-25 17:12:27 +01:00
# Provide CPU as a feature to allow listing all boards with a CPU
FEATURES_PROVIDED += cpu_$(CPU)
treewide: model newlib as a FEATURE
2021-01-26 14:55:40 +01:00
# Features that are conflicting for all architectures
FEATURES_CONFLICT += picolibc:newlib
FEATURES_CONFLICT_MSG += "Only one standard C library can be used"
drivers: Add periph/gpio_ll API Co-authored-by: Gunar Schorcht <gunar@schorcht.net> Co-authored-by: chrysn <chrysn@fsfe.org> Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com>
2021-08-27 22:58:47 +02:00
FEATURES_CONFLICT += periph_gpio_irq:periph_gpio_ll_irq
FEATURES_CONFLICT_MSG += "Only one GPIO IRQ implementation can be used"
pkg: add tinyUSB device/host stack as package
2022-09-14 09:03:56 +02:00
FEATURES_CONFLICT += periph_usbdev:tinyusb
tests: add tinyUSB CDC and MSC device test application
2022-09-30 06:59:08 +02:00
FEATURES_CONFLICT_MSG += "Package tinyUSB is not yet compatible with periph/usbdev"
Copy Permalink