Enable appsearch to perform its own hidden API processing
Previously, the hidden API encoding of the appsearch boot dex jars, i.e. those dex jars that appsearch contributes to the bootclasspath were done as part of the monolithic hidden API processing. This change causes the encoding to be done by the appsearch's bootclasspath_fragment. This change involves the following: * Addition of the fragments property to the appsearch's bootclasspath_fragment module to list all the other bootclasspath_fragment modules on which this depends. * Addition of the additional_stubs property to add stubs for APIs that are not provided by another bootclasspath_fragment. The build automatically checks that the hidden API flags which are computed by appsearch and encoded into its boot dex jars match those that are generated by the monolithic processing so this is guaranteed to be safe. Bug: 179354495 Test: m com.android.appsearch - ensure that the generated APEX is byte-for-byte identical before and after these changes. m out/soong/hiddenapi/hiddenapi-flags.csv - make sure that they are not changed by this. Change-Id: I8e5a60d64d3e147535e11a4ad30404f9888f53d2
Loading
Please register or sign in to comment