Support a list of search paths for Kconfig files #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Projects such as Zephyr OS have a module system, where Kconfig files can
exist in multiple directories that are effectively merged together by the
build system. In other words, one project directory can refer to
subdir/Kconfig where subdir/ is actually in another project directory.
As an example:
zephyr/ - main source directory
Kconfig - main Kconfig file
module/ec - module directory
motion/ - motion subsystem
Kconfig - Kconfig file for motion subsystem
Wtih the above, we might have, in zephyr/Kconfig:
source "motion/Kconfig"
and it automatically locates the file in the module/ec directory.
Add support for this, by allowing a list of search paths to be supplied to
Kconfiglib.
Signed-off-by: Simon Glass <[email protected]>
Signed-off-by: Jim Huang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Projects such as Zephyr OS have a module system, where Kconfig files can exist in multiple directories that are effectively merged together by the build system. In other words, one project directory can refer to subdir/Kconfig where subdir/ is actually in another project directory.
As an example:
Wtih the above, we might have, in zephyr/Kconfig:
and it automatically locates the file in the module/ec directory.
Add support for this, by allowing a list of search paths to be supplied to Kconfiglib.