Document OOT / app layer configuration options

bitcraze · Aug 8, 2024 · 16e9540 · 16e9540
1 parent 9c93952
commit 16e9540
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/docs/development/oot.md b/docs/development/oot.md
@@ -50,7 +50,7 @@ If you have header files in another folder, use `EXTRA_CFLAGS` in the Makefile t
 EXTRA_CFLAGS += -I$(PWD)/src/inc
 ```
 
-And since you are providing a config file by way of `$(OOT_CONFIG)` you do not need to run any make command to create a config like `make menuconfig` or `make defconfig`. Just a simple `make` will suffice.
+OOT builds can be configured with [Kbuild](https://www.bitcraze.io/documentation/repository/crazyflie-firmware/master/development/kbuild/) using terminal interfaces like `make menuconfig` or by loading a default configuration, such as with `make cf2_defconfig`. Any definitions in $(OOT_CONFIG) will override conflicting settings.
 
 ## OOT estimators
 The `config` file needs to enable ESTIMATOR_OOT, and can also set other config options:

diff --git a/docs/userguides/app_layer.md b/docs/userguides/app_layer.md
@@ -60,6 +60,10 @@ obj-y += your-app.o
 
 You can look at the applications in the `examples/` folder of the firmware repository.
 
+## Configuring the app layer
+
+The app layer can be configured with [Kbuild](https://www.bitcraze.io/documentation/repository/crazyflie-firmware/master/development/kbuild/). Default configurations can be loaded by running `make cf2_defconfig` in the app directory.  Terminal based user interfaces ('menuconfig', 'nconfig', 'gconfig', 'xconfig') can be used to configure the app layer by e.g. running `make menuconfig` in the app directory. Note that if there are any conflicting settings, the values defined in `app-config` will take priority.
+
 ## Building the app layer
 
 In order to build the app layer, go to the root folder of the app example and run: