he ECD generation appears to be bugged if the extended component is defined in two separate places. For example, the component FCS_CKM_EXT.2 is defined in two separate places in the VPN Client Module: as an additional SFR when GPOS is the Base-PP, and as an additional SFR when GPOS is the App-PP (MDF already has this SFR which is why it’s not just defined once in the mandatory SFRs section). The ECD causes each instance of the component to be defined which means there ends up being two copies of it. This may be a side effect of the workaround for #13. Perhaps if it was possible to put the actual in the section, the build script would only pick up the component that was right underneath it instead of finding two copies in the Module and adding both.
Note that this use case is specific to Modules; a PP would not have this situation come up.
he ECD generation appears to be bugged if the extended component is defined in two separate places. For example, the component FCS_CKM_EXT.2 is defined in two separate places in the VPN Client Module: as an additional SFR when GPOS is the Base-PP, and as an additional SFR when GPOS is the App-PP (MDF already has this SFR which is why it’s not just defined once in the mandatory SFRs section). The ECD causes each instance of the component to be defined which means there ends up being two copies of it. This may be a side effect of the workaround for #13. Perhaps if it was possible to put the actual in the section, the build script would only pick up the component that was right underneath it instead of finding two copies in the Module and adding both.
Note that this use case is specific to Modules; a PP would not have this situation come up.