diff options
| author | Jiyong Park <jiyong@google.com> | 2019-12-16 23:42:46 +0900 |
|---|---|---|
| committer | Jiyong Park <jiyong@google.com> | 2020-01-02 09:41:30 +0900 |
| commit | 114ff53f5e66f4493dcee443db677c09e0b9b32b (patch) | |
| tree | bcc554324ec920e920cd659b0d84635c8646e087 /java/java.go | |
| parent | e602918294cdfdb50dd2e9f246808adae932b5ce (diff) | |
m <apex_name>-deps-info prints the internal/external deps of the APEX
We need to have a way to see the list of modules that directly or
indirectly contribute to an APEX. People find it difficult to determine
whether a module is included in which APEXes because APEX tracks
indirect dependencies as well as direct dependencies. Therefore, just
looking at Android.bp for the APEX itself doesn't give the answer.
This change adds a new make target <apex_name>-deps-info, which
generates out/soong/<apex_name>-deps-info.txt file that shows the
internal and external dependencies of the said APEX.
Here, internal means the dependencies are actually part of the
APEX, while external means the dependencies are still external to the
APEX.
Bug: 146323213
Test: m (apex_test amended)
Change-Id: I33d1ccf5d1ca335d71cd6ced0f5f66b8c3886d13
Diffstat (limited to 'java/java.go')
| -rw-r--r-- | java/java.go | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/java/java.go b/java/java.go index 27f69b848..9f26e1907 100644 --- a/java/java.go +++ b/java/java.go @@ -492,6 +492,14 @@ var ( usesLibTag = dependencyTag{name: "uses-library"} ) +func IsLibDepTag(depTag blueprint.DependencyTag) bool { + return depTag == libTag +} + +func IsStaticLibDepTag(depTag blueprint.DependencyTag) bool { + return depTag == staticLibTag +} + type sdkDep struct { useModule, useFiles, useDefaultLibs, invalidVersion bool |