Skip to content

kconfig analysis #5

@matthew-l-weber

Description

@matthew-l-weber

Today's scripting doesn't look at changes in the kconfig dependency tree or the config definitions. This would be an additional analysis that should occur when considering what has changed.

REcently this tool https://github.com/alessandrocarminati/kconfig- was created which can map out kconfig trees. The backend code might expose enough meta data to use as an example to build a analysis engine for change impact of configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions