mirror of
https://github.com/espressif/esp-idf.git
synced 2026-09-22 13:01:16 +03:00
1fa10aa26a
The current base kconfgen command is stored in the __BASE_KCONFGEN_CMD build property, and it includes the --env-file option pointing to the `build/config.env` file. The `build/config.env` file does not separate component configuration files into included and excluded components, because it is created before any executable is added and we need it for the initial sdkconfig generation. The global `build/config.env` can be used for every sdkconfig format (cmake, json, txt), but not for the kconfig_menus.json format, because kconfig_menus.json relies on the Kconfig layout and hierarchy. Let's allow specifying the --env-file for each kconfgen invocation and remove it from the base kconfgen command. This allows you to specify an --env-file for each executable, each with its own config.env file. Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>