esp-idf

mirror of https://github.com/espressif/esp-idf.git synced 2026-09-22 13:01:16 +03:00

Files

Frantisek Hrbata 10c799105f fix(cmakev2/manager): seed known_components for namespace rewrite

When a component's manifest declared a managed dep `<ns>/<name>` and the
project had a local `components/<name>` shadowing it, configure failed
with `IDF: Failed to resolve component '<ns>__<name>'`.

cmakev1 does a project-wide injection so the manager's _choose_component
sees every component name in known_components and rewrites the
namespaced dep to its locally-shadowing short name. cmakev2 invokes the
manager per component with a single-component requirements file, so
known_components has only one entry and the rewrite cannot fire --
`<ns>__<name>` is written verbatim into MANAGED_REQUIRES and the
force-include at component.cmake:995 aborts.

Seed the per-component requirements file with one __COMPONENT_SOURCE
entry per discovered component so handle_project_requirements() builds
the same known_components list cmakev1 produces. The seeded entries are
inert on the cmake side -- the __component_set_property shim ignores
__COMPONENT_SOURCE -- they exist purely to feed the manager's rewrite.

Add a regression test in tools/test_build_system/buildv2/test_component.py.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>

2026-05-14 08:56:31 +02:00

__init__.py

fix(test_build_system): add __init__.py to buildv2 test directory

2026-02-18 17:29:18 +08:00

test_build_event_callbacks.py

test(cmakev2): add POST_ELF build event callback test

2026-02-24 15:17:08 +01:00

test_build.py

test(cmakev2): add test for build with IDF_COMPONENT_MANAGER=0

2026-03-23 16:02:36 +01:00

test_component.py

fix(cmakev2/manager): seed known_components for namespace rewrite