Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub components in managed lib cause errors (PACMAN-1066) #82

Open
1 task done
malachib opened this issue Feb 10, 2025 · 0 comments
Open
1 task done

Sub components in managed lib cause errors (PACMAN-1066) #82

malachib opened this issue Feb 10, 2025 · 0 comments
Labels
Status: Awaiting triage Issue is waiting for triage

Comments

@malachib
Copy link

malachib commented Feb 10, 2025

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:

PGESP-74

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.
@malachib malachib added the Status: Awaiting triage Issue is waiting for triage label Feb 10, 2025
@malachib malachib changed the title Sub components in managed lib Sub components in managed lib cause errors Feb 10, 2025
@github-actions github-actions bot changed the title Sub components in managed lib cause errors Sub components in managed lib cause errors (PACMAN-1066) Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting triage Issue is waiting for triage
Projects
None yet
Development

No branches or pull requests

1 participant