1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00

doc: fix path to build system related test applications

This commit is contained in:
Alexandre Abadie 2023-05-13 18:50:33 +02:00
parent 5f3a9de7fa
commit 0cdeafd85d
No known key found for this signature in database
GPG Key ID: 1C919A403CAE1405
3 changed files with 3 additions and 3 deletions

View File

@ -82,7 +82,7 @@ External modules can optionally define the following files:
module `foo` must be located in `<PATH_IN_EXTERNAL_MODULE_DIRS>/foo`.
An example can be found in
[`tests/external_module_dirs`](https://github.com/RIOT-OS/RIOT/tree/master/tests/external_module_dirs)
[`tests/build_system/external_module_dirs`](https://github.com/RIOT-OS/RIOT/tree/master/tests/build_system/external_module_dirs)
Pseudomodules {#pseudomodules}
=============

View File

@ -86,7 +86,7 @@ applied. Note that if any dependency issue occurs, warnings will be generated
## Application configuration with Kconfig {#app-config-kconfig}
To expose application-specific configuration options a `Kconfig` file can
be placed in the application's folder. For an example of this you can check
the [tests/kconfig](https://github.com/RIOT-OS/RIOT/tree/master/tests/kconfig)
the [tests/build_system/kconfig](https://github.com/RIOT-OS/RIOT/tree/master/tests/build_system/kconfig)
application.
## Configuration via environment variables {#env-config-kconfig}

View File

@ -379,7 +379,7 @@ In this case some special considerations must be taken with the makefiles:
`include $(RIOTBOARD)/foo-parent/Makefile.*include*`
An example can be found in
[`tests/external_board_native`](https://github.com/RIOT-OS/RIOT/tree/master/tests/external_board_native)
[`tests/build_system/external_board_native`](https://github.com/RIOT-OS/RIOT/tree/master/tests/build_system/external_board_native)
# Tools {#boards-tools}