Sub components in managed lib cause errors (PACMAN-1066) #82
Description
The Component Manager version
2.1.1
ESP-IDF Version
v5.3.2
python Version
3.11.2
Operating System
Debian x64
Browser (for https://components.espressif.com Issues)
Chrome
Description
I have a use case, say 3 libraries:
- shared
- lib1
- lib2
lib1 and lib2 both consume shared (as if shared were an sdk)
I would like to consume all 3 of these under the banner of one managed component.
A crude comparison would be the usage of esp_lcd component as contained in esp-idf repository.
If done locally via a path specified in idf_component.yml, I am able to do so
If done remotely (as we typically do with esp components) via git: I get this error:
ERROR: The "path" field in the manifest file
"/tmp/tmp8jpiou7b/src/PGESP-74/managed/components/lib1/idf_component.yml"
does not point to a directory. You can safely remove this field from the
manifest if this project is an example copied from a component repository.
To Reproduce
Issue is reproducible and observable in my proof of concept area here:
In particular, app_remote exhibits the issue while app_local does not.
If more exposition is required, please let me know.
Expected behaviour
I expect to consume a managed component and gain access to contained components also present in its repository.
Additional info
I am experimenting with the notion of a "meta" component which grabs everything. I am not married to that approach, it just felt the most viable.
The broader context for this is a graphics library with a core and then support drivers. I want to pull in the core and also the (optional) support drivers in one fell swoop using esp component manager.
I have checked existing issues and online Documentation
- I confirm I have checked existing issues and online Documentation.