mirror of
https://github.com/espressif/esp-idf.git
synced 2026-04-27 19:13:21 +00:00
Frantisek Hrbata
fc5e7eb22d
Some components simply return when included in a build for the Linux target. This is silently ignored in the `idf_component_include`, and the component interface target is linked as requirement in `idf_component_register`. This has the side effect of such components being reported as included, with their configuration displayed in the menuconfig for included components, rather than in the submenu for excluded components. For example, the `bt` component, if added as a dependency in `idf_component_register`, will be displayed in menuconfig as an included component for Linux target. The `idf_component_include` function sets the component's `COMPONENT_REAL_TARGET` property to `NOTFOUND` in such situations. Use this information when config.env is generated put such components into excluded submenu. Note that we cannot avoid linking empty component interface into library, because there might be recursive dependencies and at the time when the component is included we might not now if it has a real target or not. Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>