f57a966b66
The core problem I am trying to solve is making sure that stub libraries in Bazel have a single apex available. In Soong, this will be enforced using some graph walk which is not easy to port to Bazel. However, we might need to revisit this when we build the enforcement mechanism in Bazel. We likely need a `test_for` on the top level apex_test Bazel rule so that the test apex is _allowed_ to link against impl of the library it is trying to test. (This CL retricts this to cc_library, I can expand this to other modules if this is the right approach.) Bug: 277651159 Change-Id: Iaeec22c5626df79a33785c766ed29102b1da403e |
||
---|---|---|
.. | ||
Android.bp | ||
androidmk.go | ||
apex.go | ||
apex_sdk_member.go | ||
apex_singleton.go | ||
apex_test.go | ||
bootclasspath_fragment_test.go | ||
bp2build.go | ||
bp2build_test.go | ||
builder.go | ||
classpath_element_test.go | ||
deapexer.go | ||
key.go | ||
metadata.go | ||
metadata_test.go | ||
platform_bootclasspath_test.go | ||
prebuilt.go | ||
systemserver_classpath_fragment_test.go | ||
TEST_MAPPING | ||
testing.go | ||
vndk.go | ||
vndk_test.go |