-
Notifications
You must be signed in to change notification settings - Fork 6
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
Support if
clauses in depends_components
and depends_filepatterns
(RDT-628)
#105
Comments
if
clauses in depends_components
and depends_filepatterns
if
clauses in depends_components
and depends_filepatterns
(RDT-628)
There is another usage case, can you consider supporting something like examples/wifi: # or anchor
base_depends_components:
esp_hw_support
esp_rom
esp_wifi
examples/wifi/coexist:
add_components:
esp_coex |
@ydc-0 I think we should avoid adding more and more keywords. Maybe we can support a new feature that enhance the original yaml? That could help make the yaml anchor more useful. For example .base_depends_components: &base-depends-components
depends_components:
- esp_hw_support
- esp_rom
- esp_wifi
examples/wifi/coexist:
<<: *base-depends-components
depends_components+:
- esp_coex
depends_components-:
- esp_rom Will be interpreted into examples/wifi/coexist:
depends_components:
- esp_hw_support
- esp_wifi
- esp_coex The
|
This use case is more practical. Assume we're testing an ota related example, one config folder_foo:
depends_components:
- if: CONFIG_NAME == "eth"
components: ["esp_eth"]
- if: CONFIG_NAME == "wifi":
components: ["esp_wifi"] |
For example
To keep the similarity with others, here the folder rule should also apply the first matched
if
statement. but on extra, we support one more "default" switch case.explanation:
depends_filepatterns
should be something alike.This is also helpful when one folder contains different sdkconfig file. For example
The text was updated successfully, but these errors were encountered: