tequilaOS/platform_build_soong
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_build_soong/apex/Android.bp

46 lines
1,017 B
Text
Raw Normal View History

Add LOCAL_LICENSE_KINDS to build/soong Added SPDX-license-identifier-Apache-2.0 to: Android.bp android/Android.bp android/soongconfig/Android.bp androidmk/Android.bp apex/Android.bp bazel/Android.bp bp2build/Android.bp bpf/Android.bp bpfix/Android.bp cc/Android.bp cc/config/Android.bp cc/libbuildversion/Android.bp cc/libbuildversion/tests/Android.bp cc/ndk_api_coverage_parser/Android.bp cc/ndkstubgen/Android.bp cc/symbolfile/Android.bp cmd/dep_fixer/Android.bp cmd/diff_target_files/Android.bp cmd/extract_apks/Android.bp cmd/extract_jar_packages/Android.bp cmd/extract_linker/Android.bp cmd/fileslist/Android.bp cmd/host_bionic_inject/Android.bp cmd/javac_wrapper/Android.bp cmd/merge_zips/Android.bp cmd/multiproduct_kati/Android.bp cmd/path_interposer/Android.bp cmd/pom2bp/Android.bp cmd/pom2mk/Android.bp cmd/sbox/Android.bp cmd/soong_build/Android.bp cmd/soong_env/Android.bp cmd/soong_ui/Android.bp cmd/zip2zip/Android.bp cmd/zipsync/Android.bp cuj/Android.bp dexpreopt/Android.bp dexpreopt/dexpreopt_gen/Android.bp env/Android.bp etc/Android.bp filesystem/Android.bp finder/Android.bp finder/cmd/Android.bp genrule/Android.bp jar/Android.bp java/Android.bp java/config/Android.bp kernel/Android.bp linkerconfig/Android.bp linkerconfig/proto/Android.bp makedeps/Android.bp partner/Android.bp phony/Android.bp python/Android.bp python/tests/Android.bp remoteexec/Android.bp rust/Android.bp rust/config/Android.bp scripts/Android.bp sdk/Android.bp sh/Android.bp shared/Android.bp symbol_inject/Android.bp symbol_inject/cmd/Android.bp sysprop/Android.bp tradefed/Android.bp ui/build/Android.bp ui/logger/Android.bp ui/metrics/Android.bp ui/metrics/proc/Android.bp ui/status/Android.bp ui/terminal/Android.bp ui/tracer/Android.bp xml/Android.bp zip/Android.bp zip/cmd/Android.bp Added SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-BSD to: finder/fs/Android.bp third_party/zip/Android.bp Bug: 68860345 Bug: 151177513 Bug: 151953481 Test: m all Exempt-From-Owner-Approval: janitorial work Change-Id: Ia47ca14f16b8c9f84f9d533a07e5b00e2c04e8d4
2021-02-04 03:08:28 +01:00
package {
default_applicable_licenses: ["Android-Apache-2.0"],
}
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
bootstrap_go_package {
name: "soong-apex",
pkgPath: "android/soong/apex",
deps: [
"blueprint",
"soong",
"soong-android",
Add partial bp2build support for APEX targets (second try). Test: Added unit test Change-Id: Icbf0475251aac5d1f13bd35a18f90b6c70f3ae29
2021-07-02 13:17:16 +02:00
"soong-bazel",
Include bpf program in APEXes bpf program is put to an APEX via 'bpfs' property. It is placed under etc/bpf directory in it. Fix: 167530625 Test: m Change-Id: Ia36b486f0cffb619ecc4f7a318cde881abc5baf4
2020-09-02 10:23:38 +02:00
"soong-bpf",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"soong-cc",
android_filesystem modules can be included in APEX android_filesystem modules can be included in APEX via the new `filesystems` property. The filesystem images are placed at ./etc/fs/<modulename>.img. Bug: 172413888 Test: m nothing Change-Id: I215ca7a32ff1988a0de4e1f71397684e189839ea
2021-01-07 07:31:24 +01:00
"soong-filesystem",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"soong-java",
Prototype changes for multitree This change contains a prototype implementation for multitree. Several interfaces and modules are added. 1. Imported/Exported Modules implementing Exportable interface can export artifacts to other components. "imported_filegroup" modules can import generated artifacts from other exported modules. 2. Multitree metadata It contains information about imported/exported modules in each component, and can be generated via "m update-meta". 3. cc library stub It's based on prototype stub libraries. It uses imported/exported mechanism to expose a C API, with a map.txt file and header files. Bug: 230448564 Test: m Change-Id: Id7ff7618e2c630c5617a564d8b23b60a1cc9c8e8
2022-04-27 03:30:34 +02:00
"soong-multitree",
Export provenance metadata for prebuilt APKs and APEXes. Bug: 217434690 Test: atest --host gen_provenance_metadata_test Test: m provenance_metadata Change-Id: I91c184b6e6fe5ccfc3fc65b55b09e7a3da9502a0
2022-03-19 01:33:24 +01:00
"soong-provenance",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"soong-python",
rust modules can be included in apex We will have some APEXes having rust binaries and libraries. So, adding the support for the types of modules. rust.Module now inherits from android.ApexModuleBase and implements the android.ApexModule interface. Bug: 172414324 Test: m Exempt-From-Owner-Approval: rebased after +2 from the owner Change-Id: I356ef4c45f782a6460f001e83af96d1710642d80
2020-11-17 14:21:02 +01:00
"soong-rust",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"soong-sh",
],
srcs: [
"androidmk.go",
"apex.go",
Add apexes property to sdk Specifying an apex in the apexes propety will cause all the *classpath_fragments that are contents of the APEX to be automatically added as members of the sdk and appear in the snapshot. The purpose of this change is to dedup the APEX and sdk definitions and try and avoid some of the issues that we have been finding while attempting to build against the prebuilts. Two tests, one each for bootclasspath_fragment and systemserverclasspath_fragment, have been refactored to compare the output when adding the *fragment to the sdk directly of via the APEX. That ensures switching to use the APEX will not change the sdk snapshot unless it was previously missing a *fragment. There was also a slight difference in where the hidden API flags were copied from. That should have no impact on the output as the flags are identical. The sdk snapshot generation needed some tweaks to avoid generating a prebuilt for the APEX. Bug: 232401814 Test: m nothing Change-Id: I7aaf16a3a0ab4bebf97765d1484215cc008dc4b8
2022-05-13 15:12:19 +02:00
"apex_sdk_member.go",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"apex_singleton.go",
"builder.go",
Export default apex version from updatable_modules.go to Bazel's apex_toolchain through soong_injection. This is necessary to keep both Bazel and Soong in sync. Test: presubmit Bug: 238723069 Fixes: 238153998 Change-Id: Ibf4a8ed91d358dc7800c10e4112485a52f0606bb
2022-07-29 04:25:34 +02:00
"bp2build.go",
Export dex implementation jars from prebuilt_apex Dexpreopt and boot jars package check all require access to dex implementation jars created for java_library and java_sdk_library. They were available when building from source but not when building from prebuilts, even though they are embedded within the .apex files that are referenced from prebuilt_apex. This changes adds support to prebuilt_apex to export the dex implementation jars and updates java_import to use those exported dex implementation jars. In a source build dexpreopt/boot jars package check access the apex (or platform) specific variant of a java_library, e.g. core-oj, from which it retrieves the dex implementation jar path. After this change in a prebuilt build dexpreopt/boot jars package check behave in the same way except in this case they retrieve the dex implementation jar path from the apex (or platform) specific variant of the java_import, e.g. core-oj. The work to export files from a `.apex` file for use by other modules is performed by a new `deapexer` module type. It is not used directly in an `Android.bp` file but instead is created implicitly by `prebuilt_apex`, In order to do that this contains the following changes: * Adds a new `dexapexer` module type to handle the exporting of files from the `.apex` file. * Adds an exported_java_libs property to prebuilt_apex to specify the set of libraries whose dex implementation jars need exporting. * Creates apex specific variants of the libraries listed in the exported_java_libs property. * Adds the set of exported files to the ApexInfo to make them available to the apex specific variants. * Prevents the prebuilt_apex variants from being merged together as they will not be compatible. * Modifies java_import to use the exported file for variants of a prebuilt_apex. * Adds a ninja rule to unpack (using deapexer) the contents of the prebuilt_apex's apex file, verify that the required files are present and make them available as outputs for other rules to use. * Some minor refactorings to support these changes. * Adds tests to cover prebuilt only, prebuilt with source preferred, and prebuilt preferred with source. Test: m nothing Bug: 171061220 Change-Id: Ic9bed81fb65b92f0d59f64c0bce168a9ed44cfac
2020-11-02 18:32:38 +01:00
"deapexer.go",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"key.go",
"prebuilt.go",
Add apexFixtureFactory to apex package Unlike the similar changes in other packages this change separates the addition of the fixture factory and the conversion of the test... methods to use them as there are a few tests that need converting to use test fixtures first. Bug: 181070625 Test: m nothing Change-Id: Ic76523ba89fc1967631aeb682935935b5af116df
2021-03-08 10:47:16 +01:00
"testing.go",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"vndk.go",
],
testSrcs: [
"apex_test.go",
Rename BootImageModule to BootclasspathFragmentModule Also renames files, tests, module types in a similar fashion. There are still some references to image and boot image. They are kept for the following reasons: * image_name - this is the name of an ART boot image, i.e. the collection of .art/.oat/.vdex files. * BootImageInfo - again this is related to the ART boot image. * .../art_boot_images/... paths - ditto. Bug: 177892522 Test: m nothing Change-Id: Ie1f4738061d131fee75de48bc26a7601481bad4d
2021-04-23 15:25:28 +02:00
"bootclasspath_fragment_test.go",
Add ClasspathElement support The configuration of the bootclasspath, e.g. PRODUCT_BOOT_JARS, includes libraries that are standalone and libraries that are part of an APEX. All libraries that are part of an APEX must also be part of a bootclasspath_fragment. Currently, the libraries and fragments are handled separately but that is limiting as it does not make it easy to process all the libraries while treating those from fragments differently to standalone libraries. That is needed for hidden API processing as it needs to use classesJars from standalone libraries but pre-generated flag files from fragments. This change adds support for ClasspathElements which is represents the classpath as a whole while differentiating between standalone libraries and fragments. Bug: 177892522 Test: m nothing Change-Id: I7a4adc67164a46079eb8ec0a17fc755044b4949d
2021-06-10 09:59:41 +02:00
"classpath_element_test.go",
Add dependencies from platform_bootclasspath to contents Adds a FinalDeps mutator to add dependencies from the platform_bootclasspath to the configured boot jars which can be from either the platform or any apex. It adds dependencies for every configured boot jar, whether in ArtApexJars, BootJars or UpdatableBootJars. At the moment the dependencies are only used for testing purposes but following changes will make more use of them. Bug: 177892522 Test: m nothing Change-Id: I981305bf45bc20539a3d36987252f490e2b885cc
2021-03-22 23:09:42 +01:00
"platform_bootclasspath_test.go",
Add systemserverclasspath_fragments property to apex. - All contents of the fragment are added as java_lib dependencies. - Generated classpaths.proto is added into etc as required. Bug: 180105615 Test: m nothing Change-Id: I8e8e8b019c4ca2909182f205a47deffa946de6da
2021-05-17 22:35:26 +02:00
"systemserver_classpath_fragment_test.go",
Soong package structure refactoring Give prebuilt_etc and sh_binary their own packages and split the gigantic main Android.bp up to small, per-package ones. Test: m nothing, TreeHugger Bug: 156980228 Change-Id: I7b00cd344b9f16861f1ff39edf0029f016b853d0
2020-06-01 19:45:49 +02:00
"vndk_test.go",
],
pluginFor: ["soong_build"],
}
Reference in a new issue Copy permalink