Ticket #199068
Feature Type: feat_change_ide
Description: Currently, even though configurations can have a parent / child relationship within the configuration editor, it seems that is as far as that relationship is implemented.
However, it would be very useful if child configurations would inherit thier parents macros and override them.
Example:
We have two configurations:
CONFIG_PARENT
--- CONFIG_CHILD
If we have the following macros:
macro CONFIG_PARENT:MACRO_ONE ("parent")
macro CONFIG_PARENT:MACRO_TWO ("parent")
macro CONFIG_PARENT:MACRO_THREE("parent")
then when we select either CONFIG_PARENT or CONFIG_CHILD the three above macros will have the value "parent" defined.
if we add the following macro:
macro CONFIG_CHILD:MACRO_ONE ("child")
then the CONFIG_CHILD will have the value "child for MACRO_ONE and "parent" for the other two macros
Benefit: Make it easier to organize configurations and extend their usefulness
Link:
Ticket #199068 Feature Type: feat_change_ide Description: Currently, even though configurations can have a parent / child relationship within the configuration editor, it seems that is as far as that relationship is implemented.
However, it would be very useful if child configurations would inherit thier parents macros and override them.
Example:
We have two configurations: CONFIG_PARENT --- CONFIG_CHILD
If we have the following macros:
macro CONFIG_PARENT:MACRO_ONE ("parent")
macro CONFIG_PARENT:MACRO_TWO ("parent")
macro CONFIG_PARENT:MACRO_THREE("parent")
then when we select either CONFIG_PARENT or CONFIG_CHILD the three above macros will have the value "parent" defined.
if we add the following macro:
macro CONFIG_CHILD:MACRO_ONE ("child")
then the CONFIG_CHILD will have the value "child for MACRO_ONE and "parent" for the other two macros
Benefit: Make it easier to organize configurations and extend their usefulness Link: