Fix missing missing (min|max)_sdk_version in bootclasspath.pb
bootclasspath.pb.textproto of an apex contains min_sdk_version/max_sdk_version information of its exported libraries. It is populated using the stateful minSdkVersion/maxSdkVersion properties of the SdkLibrary module. These were previously indirectly populated by invoking `module.Library.GenerateAndroidBuildActions(ctx)`, which has been removed https://r.android.com/3079425. This CL updates the implementation to use `MinSdkVersion(ctx)` and `MaxSdkVersion(ctx)` to get the appropriate values directly and not rely on GenerateAndroidBuildActions. Bug: 345621958 Test: cat out/soong/.intermediates/packages/providers/MediaProvider/apex/com.android.mediaprovider-bootclasspath-fragment/android_common_apex30/c49cac19acc21350e0f3590de64d2f7f/bootclasspath.pb.textproto jars { path: "/apex/com.android.mediaprovider/javalib/framework-mediaprovider.jar" classpath: BOOTCLASSPATH min_sdk_version: "30" max_sdk_version: "" } jars { path: "/apex/com.android.mediaprovider/javalib/framework-pdf.jar" classpath: BOOTCLASSPATH min_sdk_version: "30" max_sdk_version: "" } jars { path: "/apex/com.android.mediaprovider/javalib/framework-pdf-v.jar" classpath: BOOTCLASSPATH min_sdk_version: "34" max_sdk_version: "" } // min_sdk_version values were empty previously Change-Id: Ia547747b16d255c1a093deee96a1abb61fd47dff
Loading
Please register or sign in to comment