Lines Matching full:uses

30 //   4. manifest fixer: a tool that adds missing <uses-library> tags to the manifests
38 // a <uses-library> tag that has the library name and an optional attribute specifying if the
43 // The libraries listed in <uses-library> tags are in the classpath of a library/app.
50 // build system uses CLC in a more narrow sense: it is a tree of libraries that represents
51 // transitive closure of all <uses-library> dependencies of a library/app. The top-level elements of
52 // a CLC are the direct <uses-library> dependencies specified in the manifest (aka. classpath). Each
53 // node of a CLC tree is a <uses-library> which may have its own <uses-library> sub-nodes.
55 // Because <uses-library> dependencies are, in general, a graph and not necessarily a tree, CLC may
60 // Example: A has <uses-library> tags B, C and D; C has <uses-library tags> B and D;
61 //          D has <uses-library> E; B and E have no <uses-library> dependencies. The CLC is:
79 // the libraries listed in the <uses-library> tags in the app's manifest as top-level CLC elements.
80 // For each of the used libraries PackageManager gets all its <uses-library> dependencies (specified
83 // <uses-library> dependencies.
89 // (other "shared" libraries that this one uses at runtime and specifies them in <uses-library> tags
93 // at runtime: <uses-library> tags in the manifests and "shared" library dependencies in
120 // A <uses-library> can be either optional or required. From dexpreopt standpoint, required library
132 // Sometimes <uses-library> tags are missing from the source manifest of a library/app. This may
134 // <uses-library>, and the library/app's manifest isn't updated to include it.
136 // Soong can compute some of the missing <uses-library> tags for a given library/app automatically
141 // Not all <uses-library> tags can be computed in this way, because some of the <uses-library>
145 // that adds a new <uses-library> dependency -- all the apps will have to be updated. That is
159 // <uses-library> dependencies of the dexpreopted library/app (including transitive dependencies).
160 // For each <uses-librarry> dependency it needs to know the following information:
162 //   - the real name of the <uses-library> (it may be different from the module name)
165 //   - all <uses-library> dependencies
175 // Some of the Java libraries that are used as <uses-library> are not SDK libraries (they are
210 // been separated into a standalone <uses-library>. Compatibility libraries should only be in the
211 // CLC if the library/app that uses them has `targetSdkVersion` less than N in the manifest.
271 			// such cases we still need to add the library to <uses-library> tags in the manifest,
320 // context map was constructed. If the implicitRootLib is itself a <uses-library>, it should be
353 // included). This is the list of libraries that should be in the <uses-library> tags in the
411 				// Return error if dexpreopt doesn't know paths to one of the <uses-library>
414 					return false, fmt.Errorf("invalid build path for <uses-library> \"%s\"", clc.Name)
416 					return false, fmt.Errorf("invalid install path for <uses-library> \"%s\"", clc.Name)