Collect container informations
This change introduces a method to collect the information of what containers (i.e. api domain, partition, or any custom defined boundaries of interest) the module belongs to. The method is called in `ModuleBase.GenerateBuildActions`. Each container objects defines the following: - name of the container - list of "restrictions", which are the containers that a module that belongs to this container is not allowed to depend on. Each "restrictions" also defines custom rules which allow bypassing the restricted dependency. Each rules are an enum that are mapped to a function, given that functions are not hashable and thus cannot be set as a value in a provider. Note that this change is a no-op, as the container information is only collected for modules that implement the "InstallableModule" interface, which is not implemented by any other module types in this change. This will be utilized in the follow-up changes. Test: m nothing --no-skip-soong-tests Bug: 338660802 Change-Id: I9d16dfec0dcf06da464aa49ee7b23f46f1da236a
This commit is contained in:
@@ -22,7 +22,7 @@ type ImageInterface interface {
|
||||
// VendorVariantNeeded should return true if the module needs a vendor variant (installed on the vendor image).
|
||||
VendorVariantNeeded(ctx BaseModuleContext) bool
|
||||
|
||||
// ProductVariantNeeded should return true if the module needs a product variant (unstalled on the product image).
|
||||
// ProductVariantNeeded should return true if the module needs a product variant (installed on the product image).
|
||||
ProductVariantNeeded(ctx BaseModuleContext) bool
|
||||
|
||||
// CoreVariantNeeded should return true if the module needs a core variant (installed on the system image).
|
||||
|
Reference in New Issue
Block a user