blob: f946587c3c3e7ddb0d8e31a96b84fe272c7504e7 [file] [log] [blame]
Jaewoong Jung525443a2019-02-28 15:35:54 -08001// Copyright (C) 2019 The Android Open Source Project
2//
3// Licensed under the Apache License, Version 2.0 (the "License");
4// you may not use this file except in compliance with the License.
5// You may obtain a copy of the License at
6//
7// http://www.apache.org/licenses/LICENSE-2.0
8//
9// Unless required by applicable law or agreed to in writing, software
10// distributed under the License is distributed on an "AS IS" BASIS,
11// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12// See the License for the specific language governing permissions and
13// limitations under the License.
14
15package android
16
17// This file contains all the foundation components for override modules and their base module
18// types. Override modules are a kind of opposite of default modules in that they override certain
19// properties of an existing base module whereas default modules provide base module data to be
20// overridden. However, unlike default and defaultable module pairs, both override and overridable
21// modules generate and output build actions, and it is up to product make vars to decide which one
22// to actually build and install in the end. In other words, default modules and defaultable modules
23// can be compared to abstract classes and concrete classes in C++ and Java. By the same analogy,
24// both override and overridable modules act like concrete classes.
25//
26// There is one more crucial difference from the logic perspective. Unlike default pairs, most Soong
27// actions happen in the base (overridable) module by creating a local variant for each override
28// module based on it.
29
30import (
31 "sync"
32
33 "github.com/google/blueprint"
34 "github.com/google/blueprint/proptools"
35)
36
37// Interface for override module types, e.g. override_android_app, override_apex
38type OverrideModule interface {
39 Module
40
41 getOverridingProperties() []interface{}
42 setOverridingProperties(properties []interface{})
43
44 getOverrideModuleProperties() *OverrideModuleProperties
45}
46
47// Base module struct for override module types
48type OverrideModuleBase struct {
49 moduleProperties OverrideModuleProperties
50
51 overridingProperties []interface{}
52}
53
54type OverrideModuleProperties struct {
55 // Name of the base module to be overridden
56 Base *string
57
58 // TODO(jungjw): Add an optional override_name bool flag.
59}
60
61func (o *OverrideModuleBase) getOverridingProperties() []interface{} {
62 return o.overridingProperties
63}
64
65func (o *OverrideModuleBase) setOverridingProperties(properties []interface{}) {
66 o.overridingProperties = properties
67}
68
69func (o *OverrideModuleBase) getOverrideModuleProperties() *OverrideModuleProperties {
70 return &o.moduleProperties
71}
72
Jiyong Park5d790c32019-11-15 18:40:32 +090073func (o *OverrideModuleBase) GetOverriddenModuleName() string {
74 return proptools.String(o.moduleProperties.Base)
75}
76
Jaewoong Jung525443a2019-02-28 15:35:54 -080077func InitOverrideModule(m OverrideModule) {
78 m.setOverridingProperties(m.GetProperties())
79
80 m.AddProperties(m.getOverrideModuleProperties())
81}
82
83// Interface for overridable module types, e.g. android_app, apex
84type OverridableModule interface {
85 setOverridableProperties(prop []interface{})
86
87 addOverride(o OverrideModule)
88 getOverrides() []OverrideModule
89
90 override(ctx BaseModuleContext, o OverrideModule)
Jaewoong Jungb639a6a2019-05-10 15:16:29 -070091 getOverriddenBy() string
Jaewoong Jung525443a2019-02-28 15:35:54 -080092
93 setOverridesProperty(overridesProperties *[]string)
Jaewoong Jungb639a6a2019-05-10 15:16:29 -070094
95 // Due to complications with incoming dependencies, overrides are processed after DepsMutator.
96 // So, overridable properties need to be handled in a separate, dedicated deps mutator.
97 OverridablePropertiesDepsMutator(ctx BottomUpMutatorContext)
Jaewoong Jung525443a2019-02-28 15:35:54 -080098}
99
100// Base module struct for overridable module types
101type OverridableModuleBase struct {
Jaewoong Jung525443a2019-02-28 15:35:54 -0800102 // List of OverrideModules that override this base module
103 overrides []OverrideModule
104 // Used to parallelize registerOverrideMutator executions. Note that only addOverride locks this
105 // mutex. It is because addOverride and getOverride are used in different mutators, and so are
106 // guaranteed to be not mixed. (And, getOverride only reads from overrides, and so don't require
107 // mutex locking.)
108 overridesLock sync.Mutex
109
110 overridableProperties []interface{}
111
112 // If an overridable module has a property to list other modules that itself overrides, it should
113 // set this to a pointer to the property through the InitOverridableModule function, so that
114 // override information is propagated and aggregated correctly.
115 overridesProperty *[]string
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700116
117 overriddenBy string
Jaewoong Jung525443a2019-02-28 15:35:54 -0800118}
119
120func InitOverridableModule(m OverridableModule, overridesProperty *[]string) {
121 m.setOverridableProperties(m.(Module).GetProperties())
122 m.setOverridesProperty(overridesProperty)
123}
124
125func (b *OverridableModuleBase) setOverridableProperties(prop []interface{}) {
126 b.overridableProperties = prop
127}
128
129func (b *OverridableModuleBase) addOverride(o OverrideModule) {
130 b.overridesLock.Lock()
131 b.overrides = append(b.overrides, o)
132 b.overridesLock.Unlock()
133}
134
135// Should NOT be used in the same mutator as addOverride.
136func (b *OverridableModuleBase) getOverrides() []OverrideModule {
137 return b.overrides
138}
139
140func (b *OverridableModuleBase) setOverridesProperty(overridesProperty *[]string) {
141 b.overridesProperty = overridesProperty
142}
143
144// Overrides a base module with the given OverrideModule.
145func (b *OverridableModuleBase) override(ctx BaseModuleContext, o OverrideModule) {
Jaewoong Junga641ee92019-03-27 11:17:14 -0700146 // Adds the base module to the overrides property, if exists, of the overriding module. See the
147 // comment on OverridableModuleBase.overridesProperty for details.
148 if b.overridesProperty != nil {
Jaewoong Jung8985d522019-06-19 11:22:25 -0700149 *b.overridesProperty = append(*b.overridesProperty, ctx.ModuleName())
Jaewoong Junga641ee92019-03-27 11:17:14 -0700150 }
Jaewoong Jung525443a2019-02-28 15:35:54 -0800151 for _, p := range b.overridableProperties {
152 for _, op := range o.getOverridingProperties() {
153 if proptools.TypeEqual(p, op) {
Jiyong Park5d790c32019-11-15 18:40:32 +0900154 err := proptools.ExtendProperties(p, op, nil, proptools.OrderReplace)
Jaewoong Jung525443a2019-02-28 15:35:54 -0800155 if err != nil {
156 if propertyErr, ok := err.(*proptools.ExtendPropertyError); ok {
157 ctx.PropertyErrorf(propertyErr.Property, "%s", propertyErr.Err.Error())
158 } else {
159 panic(err)
160 }
161 }
162 }
163 }
164 }
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700165 b.overriddenBy = o.Name()
166}
167
168func (b *OverridableModuleBase) getOverriddenBy() string {
169 return b.overriddenBy
170}
171
172func (b *OverridableModuleBase) OverridablePropertiesDepsMutator(ctx BottomUpMutatorContext) {
Jaewoong Jung525443a2019-02-28 15:35:54 -0800173}
174
175// Mutators for override/overridable modules. All the fun happens in these functions. It is critical
176// to keep them in this order and not put any order mutators between them.
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700177func RegisterOverridePostDepsMutators(ctx RegisterMutatorsContext) {
Jaewoong Jung525443a2019-02-28 15:35:54 -0800178 ctx.BottomUp("override_deps", overrideModuleDepsMutator).Parallel()
179 ctx.TopDown("register_override", registerOverrideMutator).Parallel()
180 ctx.BottomUp("perform_override", performOverrideMutator).Parallel()
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700181 ctx.BottomUp("overridable_deps", overridableModuleDepsMutator).Parallel()
Jaewoong Jung26dedd32019-06-06 08:45:58 -0700182 ctx.BottomUp("replace_deps_on_override", replaceDepsOnOverridingModuleMutator).Parallel()
Jaewoong Jung525443a2019-02-28 15:35:54 -0800183}
184
185type overrideBaseDependencyTag struct {
186 blueprint.BaseDependencyTag
187}
188
189var overrideBaseDepTag overrideBaseDependencyTag
190
191// Adds dependency on the base module to the overriding module so that they can be visited in the
192// next phase.
193func overrideModuleDepsMutator(ctx BottomUpMutatorContext) {
194 if module, ok := ctx.Module().(OverrideModule); ok {
195 ctx.AddDependency(ctx.Module(), overrideBaseDepTag, *module.getOverrideModuleProperties().Base)
196 }
197}
198
199// Visits the base module added as a dependency above, checks the module type, and registers the
200// overriding module.
201func registerOverrideMutator(ctx TopDownMutatorContext) {
202 ctx.VisitDirectDepsWithTag(overrideBaseDepTag, func(base Module) {
203 if o, ok := base.(OverridableModule); ok {
204 o.addOverride(ctx.Module().(OverrideModule))
205 } else {
206 ctx.PropertyErrorf("base", "unsupported base module type")
207 }
208 })
209}
210
211// Now, goes through all overridable modules, finds all modules overriding them, creates a local
212// variant for each of them, and performs the actual overriding operation by calling override().
213func performOverrideMutator(ctx BottomUpMutatorContext) {
214 if b, ok := ctx.Module().(OverridableModule); ok {
215 overrides := b.getOverrides()
216 if len(overrides) == 0 {
217 return
218 }
219 variants := make([]string, len(overrides)+1)
220 // The first variant is for the original, non-overridden, base module.
221 variants[0] = ""
222 for i, o := range overrides {
223 variants[i+1] = o.(Module).Name()
224 }
225 mods := ctx.CreateLocalVariations(variants...)
Jaewoong Jung26dedd32019-06-06 08:45:58 -0700226 // Make the original variation the default one to depend on if no other override module variant
227 // is specified.
228 ctx.AliasVariation(variants[0])
Jaewoong Jung525443a2019-02-28 15:35:54 -0800229 for i, o := range overrides {
230 mods[i+1].(OverridableModule).override(ctx, o)
231 }
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700232 } else if o, ok := ctx.Module().(OverrideModule); ok {
233 // Create a variant of the overriding module with its own name. This matches the above local
234 // variant name rule for overridden modules, and thus allows ReplaceDependencies to match the
235 // two.
236 ctx.CreateLocalVariations(o.Name())
Jaewoong Jung26dedd32019-06-06 08:45:58 -0700237 // To allow dependencies to be added without having to know the above variation.
238 ctx.AliasVariation(o.Name())
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700239 }
240}
241
242func overridableModuleDepsMutator(ctx BottomUpMutatorContext) {
243 if b, ok := ctx.Module().(OverridableModule); ok {
Jaewoong Jung26dedd32019-06-06 08:45:58 -0700244 b.OverridablePropertiesDepsMutator(ctx)
245 }
246}
247
248func replaceDepsOnOverridingModuleMutator(ctx BottomUpMutatorContext) {
249 if b, ok := ctx.Module().(OverridableModule); ok {
Jaewoong Jungb639a6a2019-05-10 15:16:29 -0700250 if o := b.getOverriddenBy(); o != "" {
251 // Redirect dependencies on the overriding module to this overridden module. Overriding
252 // modules are basically pseudo modules, and all build actions are associated to overridden
253 // modules. Therefore, dependencies on overriding modules need to be forwarded there as well.
254 ctx.ReplaceDependencies(o)
255 }
Jaewoong Jung525443a2019-02-28 15:35:54 -0800256 }
257}