mirror of
https://github.com/espressif/esp-idf.git
synced 2026-06-07 05:36:32 +03:00
df6ee7dc26
The build system currently suffers from a bug where custom configuration settings are lost when the component manager is invoked multiple times. During an initial reconfigure or set-target command, the component manager may return no managed components. Because the build system lacks the Kconfig definitions for these components at this stage, it automatically prunes any related configuration symbols—specifically those defined in managed component Kconfig files—from the sdkconfig file. By the time the component manager finishes downloading the dependencies in a subsequent run, these original settings have already been overwritten and discarded because they were previously unrecognized by the build system. To resolve this, the generation of the final sdkconfig should be deferred until all component manager resolution cycles are complete. We need to ensure that the build system does not treat missing Kconfig definitions as invalid until the full dependency graph is loaded. A potential fix involves using a temporary configuration file for intermediate component manager passes to prevent the main sdkconfig from being prematurely scrubbed of valid user settings that belong to yet-to-be-resolved components. Edit: Added cleanup of sdkconfig.cm file and comments Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com> Edited by: Daniel Paul <daniel.paul@espressif.com>