am skip reason: Change-Id I5d5326f415352d50ace7f456d29b257d1d769318 with SHA-1 8aa401023b is in history
Change-Id: I93a339c9af7ed0e83a24bd8b08d14e82513f9434
am skip reason: Change-Id I5881e5ee7c2169c30f544882344a60a602dae917 with SHA-1 87a05a389d is in history
Change-Id: I15da603bd2cde25d1c6b7735ff1ee06904159abc
This reverts commit 7871416eec.
Reason for revert: This change is breaking CtsNNAPITestCases.TensorRankConstraint (http://b/156464649).
Change-Id: I8831993a7d3c2079a8d76a23dfbdf9c7c1543181
Allow the sdk_version against which the stubs for a scope are compiled
to be specified in the module on a per scope basis.
Bug: 155164730
Test: m nothing
Merged-In: I5881e5ee7c2169c30f544882344a60a602dae917
Change-Id: I5881e5ee7c2169c30f544882344a60a602dae917
(cherry picked from commit 87a05a389d)
JNI libs for "updatable" APKs or APKs in "updatable" APEXes should set
sdk_version which is equal to or less than APK's min_sdk_version.
In fact, we'd better check if min_sdk_version of JNI libs matches(or is
earlier than) min_sdk_version of the APK. But for now the build system
can't handle sdk_version/min_sdk_version correctly for JNI libs. That's
why sdk_version of JNI libs is enforced to match with min_sdk_version
of APK in this change.
(original commit: 98c4750f39)
Bug: 145796956
Test: m
Change-Id: I08543ccee7dfda0559a1fca108ceb5c28f84943f
am skip reason: Change-Id Iee7a9ab9d816ed1948e2c7cde23f9907cfda337d with SHA-1 36c5b8d0b8 is in history
Change-Id: I366d3539e4585e9f013d90330a900178bc0eff19
am skip reason: Change-Id I8a9c9c5a1bdceaee387c08864ae2b34629e0d46f with SHA-1 51084ff6cf is in history
Change-Id: Ib818feda122049c3b02d415efe759702eaeeba6b
am skip reason: Change-Id Ic859a61de155b3e582c17f6ab5e9298f5f4e709a with SHA-1 6c9c5fc4bc is in history
Change-Id: Idffd5de681a123a5cea7f88eb852526dab2c3e44
am skip reason: Change-Id I966e82b8ae67624da168e05f5a2b062b832cb8cd with SHA-1 dd9d0740fa is in history
Change-Id: I10da6a3bff1f8da9e777f8aded587281b81bb7ef
am skip reason: Change-Id I708657661188ea4a14a4dd8c6bc4b46237bbe5e0 with SHA-1 1b1e8069ec is in history
Change-Id: I7584cd25b318e30f7db6955f6d7c1696d9a3c973
am skip reason: Change-Id I9be9aab07252b491ab292b8847138a93b487cf53 with SHA-1 c3091c8c19 is in history
Change-Id: I24c72ebda8a236ec1b9a4d352ac1de52729b52cf
am skip reason: Change-Id Iea7d59852d7aeb503120acf3c44e08eb0d9d07b9 with SHA-1 0ff08bdb07 is in history
Change-Id: Ieaeaff0b5562874ba3683c461e4da14f47e7cec9
am skip reason: Change-Id Icf7c20dc109a773430768c1a2d91c674551dbc1b with SHA-1 780c5f4715 is in history
Change-Id: I70bf9330beaa98207950cdc67025f4804b9a9f48
am skip reason: Change-Id Iffce78cbce88a8341146bf19e78acf25fc69f2b0 with SHA-1 e5c3b85ee5 is in history
Change-Id: Ifc42a41c13d4654e574ee672cf9708a1390880d6
am skip reason: Change-Id I87ca5a942228cf6af1a9939f0334d6fc46c39a63 with SHA-1 160fe41c39 is in history
Change-Id: Ife1c3e7c7d9d2d27329320bfc1b2efce00c902ed
Visibility rules can be 'inherited' in one of two ways. Either from
defaults or from a module that called ctx.CreateModule(...).
Previously, in both cases the inheriting module could only append
additional visibility rules to the end of the inherited rules. That
made it impossible to restrict the visibility by removing or ignore
inherited rules.
The //visibility:override rectifies that by allowing the inheriting
module to ignore all the rules that they would have inherited. It can
only go at the beginning of a list of rules specified in a module but
after defaults are applied it can end up in the middle of a list of
rules. In that case it behaves as if all the rules up to and including
the //visibility:override rule were discarded.
It can be used with //visibility:private to override
//visibility:public and vice versa.
Bug: 155787200
Test: m nothing
Merged-In: I8a9c9c5a1bdceaee387c08864ae2b34629e0d46f
Change-Id: I8a9c9c5a1bdceaee387c08864ae2b34629e0d46f
(cherry picked from commit 51084ff6cf)
Allow the sdk_version against which the stubs for a scope are compiled
to be specified in the module on a per scope basis.
Bug: 155164730
Test: m nothing
Change-Id: I5881e5ee7c2169c30f544882344a60a602dae917
Matches the naming scheme used by the separate manually created modules
that will be replaced by java_sdk_library's automatically created
components. This will simplify conversion to java_sdk_library as it
will allow developers to concentrate on getting the conversion correct
without also having to worry about name changes. It will also allow the
conversions to be parallelized as many of the references to the
components are in places where conflicts are likely.
Test: m nothing
Bug: 155480189
Merged-In: Ic859a61de155b3e582c17f6ab5e9298f5f4e709a
Change-Id: Ic859a61de155b3e582c17f6ab5e9298f5f4e709a
(cherry picked from commit 6c9c5fc4bc)
The constants are only used in one place in the code and in the test.
This change switches the test code to use the apiScope methods to
generate the names and then inlines the constants in those methods. It
makes it easier to see the naming convention.
Test: m nothing
Bug: 155480189
Merged-In: I966e82b8ae67624da168e05f5a2b062b832cb8cd
Change-Id: I966e82b8ae67624da168e05f5a2b062b832cb8cd
(cherry picked from commit dd9d0740fa)
