Lines Matching refs:apex
26 // is destined for an apex or not (installed to one of the regular partitions).
29 // APEX, it should depend only on stable interfaces such as NDK, stable AIDL,
33 // variations by apex.apexMutator if it is directly or indirectly included
34 // in one or more APEXs. Specifically, if a module is included in apex.foo and
35 // apex.bar then three apex variants are created: platform, apex.foo and
36 // apex.bar. The platform variant is for the regular partitions
43 // Marks that this module should be built for the APEX of the specified name.
44 // Call this before apex.apexMutator is run.
47 // Returns the name of APEX that this module will be built for. Empty string
50 // multiple modules each of which for an APEX. This method returns the
51 // name of the APEX that a variant module is for.
52 // Call this after apex.apexMutator is run.
59 // Tests if this module could have APEX variants. APEX variants are
61 // for not creating APEX variants for certain types of shared libraries
65 // Tests if this module can be installed to APEX as a file. For example,
71 // for an APEX marked via BuildForApex().
74 // Sets the name of the apex variant of this module. Called inside
80 // Name of the apex variant that this module is mutated into
84 // Provides default implementation for the ApexModule interface. APEX-aware
153 // apexNamesMap()["foo"]["bar"] == true: module foo is directly depended on by APEX bar
154 // apexNamesMap()["foo"]["bar"] == false: module foo is indirectly depended on by APEX bar
155 // apexNamesMap()["foo"]["bar"] doesn't exist: foo is not built for APEX bar
163 // depended on by an APEX named apexName. Directly depending means that a module
164 // is explicitly listed in the build definition of the APEX via properties like
177 // Tests whether a module named moduleName is directly depended on by an APEX
192 // Tests whether a module named moduleName is directly depended on by any APEX.
195 // Host has no APEX.
211 // direct and indirect dependencies) by any APEX.
