Skip to content

Conversation

jserv
Copy link
Contributor

@jserv jserv commented Oct 5, 2025

This adds visibility of symbol dependency origins to help users realize why configuration values are being forced.

When a symbol is controlled by select or imply statements, the main menu now displays which symbols are doing the controlling:

  -*- Crypto Library [selected by FEATURE_A, FEATURE_B]

The symbol information window also shows the origin:

  Value: y
    (selected by: FEATURE_A, FEATURE_B)

This eliminates the need to manually search through Kconfig files to understand dependency relationships.

This adds visibility of symbol dependency origins to help users realize
why configuration values are being forced.

When a symbol is controlled by select or imply statements, the main
menu now displays which symbols are doing the controlling:
  -*- Crypto Library [selected by FEATURE_A, FEATURE_B]

The symbol information window also shows the origin:
  Value: y
    (selected by: FEATURE_A, FEATURE_B)

This eliminates the need to manually search through Kconfig files to
understand dependency relationships.
@jserv jserv merged commit 772ea41 into main Oct 5, 2025
7 checks passed
@jserv jserv deleted the symbol-visibility branch October 5, 2025 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant