Build-Time Configuration
Every build-time option in this SDK is a Kconfig symbol. The names follow a small set of rules.
This page describes the naming rules. For what an individual option does, read its help text.
Prefixes
A symbol’s prefix names the component that defines it, not the components that read it:
Prefix |
Owner |
|---|---|
|
the node components: |
|
the OS abstraction layer |
|
the example helper components |
|
the test-only components |
Vendored code and copies of ESP-IDF symbols keep the upstream name.
Migration from older names
A component’s sdkconfig.rename maps old symbols to the current ones. The ESP-IDF build then converts an old sdkconfig without manual edits. A file has one or both of these blocks:
Symbols that an earlier RainMaker Neo release used.
RainMaker classic symbols with a 1:1 equivalent, for example
CONFIG_ESP_RMAKER_SCHEDULING_MAX_SCHEDULEStoCONFIG_ESP_RMAKER_NEO_SCHEDULING_MAX_SCHEDULES.
A classic symbol with a different meaning, type or default has no entry. Set its Neo equivalent by hand.
The POSIX build does not read sdkconfig.rename. Update a POSIX sdkconfig by hand.
Two migrations need manual edits also on ESP-IDF:
espressif/rmaker_app_networkdefaultsAPP_NETWORK_FACTORY_NVS_PARTITION_NAMEandAPP_NETWORK_PROV_DATA_NAMESPACEto the classicESP_RMAKER_FACTORY_*names. A project that rebuilds from itssdkconfig.defaultsgets the literal string"ESP_RMAKER_FACTORY_PARTITION_NAME", and cannot open the factory partition. Add the four lines fromexamples/common/app_network/README.mdtosdkconfig.defaults. A project that keeps itssdkconfigis not affected.Neo has no self claiming. In classic,
ESP_RMAKER_ASSISTED_CLAIMis one option of theESP_RMAKER_CLAIM_TYPEchoice. The rename keeps the entry for earlier Neo projects, so a classic project with self claiming getsCONFIG_ESP_RMAKER_NEO_ASSISTED_CLAIM=nand no device credentials. SetCONFIG_ESP_RMAKER_NEO_ASSISTED_CLAIM=y, or pre-flash the device credentials.