aboutsummaryrefslogtreecommitdiff
path: root/apex/apex_test.go
Commit message (Collapse)AuthorAgeFilesLines
...
* | Tag apex_set's 'set' config with `android:"path"`Pranav Gupta2022-09-271-0/+22
|/ | | | | | | | This allows apex_set's set config to use other soong modules as a dependency Bug:249169376 Change-Id: I8da20c6f474328d63d9aa3811f94e3e04b89ea4c Test: Added a test case to check soong module assignment to the set field of an apks_set rule
* Use PackedAdditionalOutputs when reading apk_set for canned_fs_configJiyong Park2022-09-261-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | When an app_set module is included in an APEX, we don't use its `builtFile` which is the main APK, , but `PackedAdditionalOutputs()` which is the zip file where all APK files (main + additional) files are packed. We then unzip them into the corresponding directory inside the APEX. However, `buildFile` still has been used when constructing canned_fs_config whose content should match with what are actually included in the APEX. Fixing the bug by using `PackedAdditionalOutputs()` instead. Bug: 236299724 Test: m nothing (apex_test.go amended) Test: follow https://buganizer.corp.google.com/issues/236299724#comment34 * mkdir for-236299724 * cd for-236299724 * repo init -u https://android.googlesource.com/platform/manifest -b * master --partial-clone --clone-filter=blob:none * repo sync -c -j8 * unzip -l ~/Downloads/mainline_t_2022_jun_t1004275.zip | cut -c31- | grep | xargs rm -f * unzip ~/Downloads/mainline_t_2022_jun_t1004275.zip * source build/envsetup.sh * choosecombo 1 aosp_arm64 userdebug * m com.android.extservices.gms Change-Id: If9752c07748300dbb963568de4e879b041b0a206
* add jacocoagent by default to Java modulesSam Delmerico2022-09-091-13/+1
| | | | | | | | | | | | | | On coverage builds, R8 will fail to properly optimize and fail the build if ignore_warnings: false, because jacoco injects dependencies on jacocoagent classes, but the jacocoagent library is not part of the classpath libraries passed in to R8 in its arguments. Instead we can add jacocoagent as a libs dependency for these modules so that it will get pulled into the r8 flags. Bug: 243903417 Test: m Change-Id: Icc24cc260b896fc800125a0318308d823ccf7a83
* jacoco libs dependency for instrumented librariesSam Delmerico2022-08-311-0/+10
| | | | | | | | | | | | | | | | | | | | On coverage builds, R8 will fail to properly optimize and fail the build if ignore_warnings: false, because jacoco injects dependencies on jacocoagent classes, but the jacocoagent library is not part of the classpath libraries passed in to R8 in its arguments. Instead we can add jacocoagent as a libs dependency for these modules so that it will get pulled into the r8 flags. Bug: 243903417 Test: add optimize.ignore_warnings: false to NetworkStackAppDefaults && make SKIP_ABI_CHECKS=true PRODUCT=cf_x86_phone-userdebug \ EMMA_INSTRUMENT=true EMMA_INSTRUMENT_FRAMEWORK=true \ CLANG_COVERAGE=true COVERAGE_PATHS="" \ TARGET_USERDATAIMAGE_PARTITION_SIZE=17179869184 \ SKIP_BOOT_JARS_CHECK=true \ NetworkStack Change-Id: I71313b1fd35437ec52890f5c30b3fd1381c7c3d2
* Merge "Introduce cc_api_library"Treehugger Robot2022-08-101-0/+58
|\
| * Introduce cc_api_libraryKiyoung Kim2022-08-101-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce cc_api_library, which reflects imported API from other inner-tree. This cc_api_library module type will later refer from the other ninja module which generates stub library from the interface description. Tested environment : * original libc definition has been removed temporarily, to ensure that imported api stub library is being used from build * Added new definition of libc as below cc_api_library { name: "libc", arch: { x86: { src: "libs/x86/libc.so", }, x86_64: { src: "libs/x86_64/libc.so", }, }, header_libs: [ "libc_headers", ], export_header_lib_headers: ["libc_headers"], min_sdk_version: "9", vendor_available: true, } Bug: 236087698 Test: `ALLOW_MISSING_DEPENDENCIES=true m vendorimage` succeeded Change-Id: I67070b0f3561aa2afd73b6c1c0fdf4255218baac
* | Remove obsolete notice property.Bob Badour2022-07-291-2/+0
| | | | | | | | | | | | | | | | Bug: 192434786 Test: m droid dist Change-Id: I0f384ae895cebab9732448b82db600c67eb8f711
* | Merge "Disallow '_' in bpf source name"Ken Chen2022-07-281-9/+9
|\ \ | |/ |/|
| * Disallow '_' in bpf source nameKen Chen2022-07-071-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current design: 1. The bpf compiled object name is derived from the source name (e.g. foo.c -> foo.o). 2. Full bpf program/map name are concatenated by object name + '_' + program/map name in run-time. (e.g. obj name: x.o; program name: y_z; full bpf program name will be x_y_z) Issue: x.o with map y_z and x_y.o with map z can cause naming collision in run-time, since both result in x_y_z. This commit prevents it from happening with a build-time check. Bug: 236706995 Test: m Change-Id: Ic03bfcf07a5748ed63246b71d5ae8de0405e658a
* | Distinguish # apex and # systemapi symbolsJiyong Park2022-07-191-4/+6
|/ | | | | | | | | | | | | | | Previously, the symbol tag `# apex` was treated the same as `# systemapi`. With this CL, they have different meanings. `# systemapi`: APIs that are defined in the platform (the non-updatable part), and are exposed to unbundled system components like APEX `# apex`: APIs that are defined in the APEX and are exposed to the platform or other APEXes Bug: 239274367 Test: m Change-Id: I0484ea349656dbbd337e5fe3a5970f0ad275b807
* Treat <x> and <x>_compressed prebuilt APEXes as being equivalentPaul Duffin2022-06-131-1/+102
| | | | | | | | | | | | | | | | (cherry picked from commit 1aa50564c783e4134e2fb4a7cdd0abca5b7b1403) When extracting dex files from prebuilt APEXes the build fails if it finds two or more prebuilt APEXes that could provide the dex files. This change treats <x> and <x>_compressed APEXes as being the same and always selects the uncompressed APEX. Bug: 235284603 Test: m nothing # Added TestDuplicateButEquivalentDeapexersFromPrebuiltApexes # Failed without this change, works with it. Merged-In: I805cb9dfa9f590c91585d75c4f4586b212b73d41 Change-Id: I805cb9dfa9f590c91585d75c4f4586b212b73d41
* bootclasspath_fragment: Require at least one hidden_api package propertyPaul Duffin2022-05-271-0/+24
| | | | | | | | | | | | | | | | Previously, the split_packages, single_packages and package_prefixes properties were all optional and the split_packages defaulted to ["*"]. As that value conflicted with the other package properties that meant that split_packages always had to be specified even if it was to just set it to an empty array. This change requires at least one of them to be specified and defaults split_packages to an empty list which means it is not required, although it can be helpful to make that explicit. Bug: 194063708 Test: m nothing Change-Id: I5a4c2d68e72e39f5c4a2441326dfce8685fc8ff2
* Pass pointer to dependencyTag instead of copying structPaul Duffin2022-05-131-1/+1
| | | | | | | | | | | | | | | | A follow up change will add some more fields to the tag which will make passing the struct around by value will get more expensive. Switching to pointers will make this slightly more efficient. Changing the type of the tags from dependencyTag to *dependencyTag broke a test. Rather than simply patch the test and then maybe have to patch it again in the next change this adds a a String() method that will insulate the test from being affected by changes in the dependencyTag contents. Bug: 232401814 Test: m nothing Change-Id: I23da742ebffb74ef3b9b68f772519ceb38332f5f
* Merge changes Ie8881b85,I6c064f8aSpandan Das2022-05-101-0/+64
|\ | | | | | | | | | | * changes: Enforce updatable=true on apps of updatable apexes Update sdk_version check for jni_libs of updatable apps
| * Enforce updatable=true on apps of updatable apexesSpandan Das2022-05-101-0/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Update apex_info (a topdown mutator) so that it sets updatable=true on apps of updatable apexes - Write a unit test that tests different combinations of updatable/non-updatable apks-in-apexes - Update an existing unit test that asserts a different error Test: go test ./java Test: m nothing (in internal) Bug: 209409604 Change-Id: Ie8881b857afcec44addf27fc360c5b8abf726bd2
* | Revert "Append APEX version instead of build ID for APK-in-APEX ..."Oriol Prieto Gasco2022-05-051-13/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | Revert submission 2067907-apk-in-apex Bug: 230873680 Reason for revert: Change broke aab generation b/230873680 Reverted Changes: I9cef1418c:Append APEX version instead of build ID for APK-in... Ic37eeba8b:Make apexer replace instances of version placehold... Change-Id: Ib113d56901e815435f71bf878049cdabd210503c
* | Append APEX version instead of build ID for APK-in-APEX paths.Jingwen Chen2022-04-211-44/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL removes the build_id.mk suffix and replaces it with a hardcoded placeholder string that will be replaced with the actual version in apex_manifest.json by apexer at apex construction time. This means that as long as the apex version is incremented, the APK-in-APEX will be installed to a new directory path from the package manager's perspective. Fixes: 229574810 Bug: 229625490 Bug: 226559955 Bug: 224589412 Bug: 227417611 Bug: 228157333 Bug: 228803590 Bug: 229136249 Test: atest StrictJavaPackagesTest Test: soong tests Test: deapexer list out/dist/com.google.android.permission.apex Change-Id: I9cef1418c3fc7e0970d96995b8398f5e82f479e0
* | Suffix the build ID to the dirname of APK-in-APEX files.Jingwen Chen2022-04-191-13/+44
|/ | | | | | | | | | | This fixes an issue with package manager's cache invalidation. Test: CI Bug: 226559955 Bug: 224589412 Change-Id: I8af49d51ff99cf8184d0e4d1136fff1cdb29c23e Merged-In: I8af49d51ff99cf8184d0e4d1136fff1cdb29c23e
* Merge "Remove apex10000_private variants"Jiyong Park2022-04-121-2/+2
|\
| * Remove apex10000_private variantsJiyong Park2022-04-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a library is included in two APEXes whose platform_apis settings are different, two apex variants of the library is created: apex1000 and apex1000_private. This change was introduced with ag/15061306, especially by the commit [1]. However, that part should be reverted because it actually creates unnecessary variants. It's unnecessary because the two variants of the library are compiled (excluding the linking) exactly the same. If a private symbol of its dependency was actually used when compiling the apex1000_private variant, then the other apex1000 variant wouldn't have been built because that private symbol must have caused a linkage error. [1] https://googleplex-android-review.git.corp.google.com/c/platform/build/soong/+/15061306/2..4/android/apex.go#b527). Bug: 228785792 Test: m Change-Id: Id58d3e98a51de5e628ca72ef86e9cd11b0ee8971
* | Move proguard test files to java packageColin Cross2022-04-111-38/+36
|/ | | | | | | | The proguard test files are duplicated in apex and sysprop and will be needed by app tests, move them to the java package. Test: run all soong tests Change-Id: Ie13817dcda8d98801d16a97ffceef1100c7d5380
* Flag to globally override apexes' min_sdk_versionAlbert Martin2022-04-081-0/+124
| | | | | | | | | | Override all mainline updateable apexes' min_sdk_version to same version to get single shared native libs on DCLA. Test: Run "vendor/google/build/go/mainline_go_modules_arm.sh" and inspect built apexes Bug: 212609891 Change-Id: Ide7d3f2bc772ac6240f1c917b87285d051d6f605 Merged-In: Ide7d3f2bc772ac6240f1c917b87285d051d6f605
* Export provenance metadata for prebuilt APKs and APEXes.Wei Li2022-04-051-4/+24
| | | | | | | | Bug: 217434690 Test: atest --host gen_provenance_metadata_test Test: m provenance_metadata Change-Id: I91c184b6e6fe5ccfc3fc65b55b09e7a3da9502a0
* Change permitted_packages check to be per-jar rather than per-apexSpandan Das2022-04-041-13/+54
| | | | | | | | | | | | | | | | | | (cherry-pick of ag/17524387 into aosp) Summary: - updates the Q and R maps, the new keys are the bcp jars and not the apexes. neverallow build rules ensure that these bcp jars have a restricted set of permitted_packages - remove BootclasspathJar from the neverallow rule. This is no longer necessary since the keys in the maps are the bootjars themselves, and not apexes Bug: 205289292 Test: In build/soong, go test ./apex Change-Id: Icb91de934181a8b6f085e03a0ce8c5e08504ff94 Merged-In: Icb91de934181a8b6f085e03a0ce8c5e08504ff94 (cherry picked from commit 440ff9672846ecbc6d607ae65ea6826c49552756)
* Revert "Relax apex package restriction for T+ jars"Anton Hansson2022-04-041-82/+2
| | | | | | | | | | This reverts commit 1fdd6ca88a192c61abe31d2f7a7f5721cafca1f8. Reason for revert: b/205289292 tracks the real fix for this Test: presubmit Change-Id: I5a2edaf4f930dafa26659f85d9425e9041c72275 Merged-In: I5a2edaf4f930dafa26659f85d9425e9041c72275
* Revert "Revert "Build notice files from license metadata.""Bob Badour2022-04-011-9/+0
| | | | | | | | This reverts commit 77807b3c277723161a193aea2a9df1e464448c3d. Reason for revert: fix and roll forward again Change-Id: I80c796ca81ecf29df9522babe54d684a0d11b9e6
* Revert "Build notice files from license metadata."Wei Sheng Shih2022-04-011-0/+9
| | | | | | | | | | | | | This reverts commit 43c2dcaef609c4a268bfab6c95ed924af4ead6b1. Reason for revert: suspect build break Bug: 227682036 Test: TARGET_BUILD_VARIANT=userdebug UNBUNDLED_BUILD_SDKS_FROM_SOURCE=true vendor/google/build/mainline_modules_bundles.sh -j97 Change-Id: Ibfb8b4fefc264f52f32ba661c269a9cd625d800a
* Build notice files from license metadata.Bob Badour2022-03-311-9/+0
| | | | | | | | | | | Switch from generate-notice-files.py and mergenotice.py to htmlnotice. Bug: 151177513 Bug: 213388645 Bug: 210912771 Test: m droid dist reportmissinglicenses Change-Id: I6cac049d24f35ec358c6f341a04f4ba6161703bf
* Merge changes I4c373b29,I9ccda6fc,I1b390b0e,I30151217Spandan Das2022-03-241-0/+179
|\ | | | | | | | | | | | | | | * changes: Do not propagate strict updatability linting to libcore/ Create allowlist to skip strict updatability lint check Propagate strict_updatability_linting to transitive deps of updatable apexes Export LintDepSetsIntf from java package
| * Do not propagate strict updatability linting to libcore/Spandan Das2022-02-231-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | propogation of this flag is determined by the location of the Android.bp where a library is defined. libcore/ libraries that are transtive deps of updatable apexes will - inherit strict_updatability_linting:true if defined in libcore root - not inherit strict_updatability_linting:true if defined in libcore subdir Note that the module can explicitly list `lint:{strict_updatability_linting: true}' in their Android.bp file, in which case they will not be allowed to baseline NewApi errors Test: m lint-check Test: TH Bug: 208656169 Bug: 182349282 Change-Id: I4c373b2960a7af16301d7f06aab448f39b937ea9
| * Propagate strict_updatability_linting to transitive deps of updatable apexesSpandan Das2022-02-081-0/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create a topdown mutator to walk the deps of updatable apexes. If a dep is lintable, set its strictUpdatabilityLinting to true Creating a new mutator after apexInfoMutator makes it easy to maintain an allowlist (e.g. override_apex does not require an entry in the allowlist, its canonical name can be retrieved using ApexVariationName()) Test: In build/soong/, go test ./apex Test: TH Bug: 182349282 Change-Id: I1b390b0e3a8fb20754ce50c6b253d68d2b3f263b
* | Use single module for clang runtime librariesColin Cross2022-03-071-4/+6
| | | | | | | | | | | | | | | | | | | | The clang prebuilts now provide a single module with per-architecture variants instead of a module per architecture. Bug: 220019988 Test: m checkbuild Change-Id: I39e2cf8ae14edf8510276dab38011afaef85822c Merged-In: I39e2cf8ae14edf8510276dab38011afaef85822c
* | Merge "Support overriding APEX java contents"Remi NGUYEN VAN2022-03-031-0/+85
|\ \
| * | Support overriding APEX java contentsRemi NGUYEN VAN2022-03-021-0/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In addition to the current "apps", support overriding bootclasspath_fragments, systemserverclasspath_fragments, and java_libs. This is useful to build APEXes with slightly different contents, for example where the base APEX could contain libraries that only use stable APIs, but the overriding APEX could contain a variant that also uses non-finalized APIs. Bug: 222247869 Test: m (runs apex tests) Change-Id: I14da6f835c58b44be31e517598695ec8ff830648
* | | Merge "Install required deps for flattened APEX."Jiakai Zhang2022-02-281-0/+32
|\ \ \ | |/ / |/| |
| * | Install required deps for flattened APEX.Jiakai Zhang2022-02-281-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The primary boot image is a required dep of the ART APEX. It needs to be installed no matter the APEX is flattened or not. Bug: 220991677 Test: 1. m OVERRIDE_TARGET_FLATTEN_APEX=true com.android.art 2. See boot.art in /system/framework/<isa> Change-Id: I1a69ae1b86df97fc44ea6c75c8bb9ec960c8d249
* | | Merge "apex: track transitive dependencies of rust jni lib"Treehugger Robot2022-02-241-2/+31
|\ \ \ | |/ / |/| |
| * | apex: track transitive dependencies of rust jni libJiyong Park2022-02-241-2/+31
| |/ | | | | | | | | | | | | | | | | dependencies of rust library registered as jni_lib are correctly tracked. Bug: 220397949 Test: m nothing Change-Id: I43016a77656d04f59f798b02d541c6a19288ec9c
* / apex supports ".apex" tagJooyung Han2022-02-241-0/+48
|/ | | | | | | | Tests can embed non-compressed .apex output with the tag. Bug: 221024307 Test: soong test Change-Id: Id4a239d1897237105a064cea8c97029f5b996a98
* VNDK libs use "unique" APEX variantsJooyung Han2022-02-041-18/+94
| | | | | | | | | | | | | | | | | | | | | | | In case there are two vendor apexes(one with "use_vndk_as_stable:true", and the other with "use_vndk_as_stable:false") a VNDK lib used by both will have "APEX" variant and the former APEX will use "apex" variation. For example, apex1(use_vndk_as_stable) -> foo -> libvndk apex2 -> bar -> libvndk Since foo, bar and libvndk are mutated into two APEX variations("", "apex10000"), foo will use the apex variation of libvndk. To fix this, VNDK libs can use "unique" APEX variations. Then, in the above example, foo will have "myapex1" variation and libvndk will have two APEX variations("" and "apex2"). So foo will link to ""(non-APEX) variation as fallback. Bug: 216847402 Test: m nothing (soong tests) Change-Id: I116932860ef79e22dc338a58b251e3ca693ab4f3
* use_vndk_as_stable APEX shouldn't include VNDK libJooyung Han2022-02-041-0/+17
| | | | | | | | | | | | | | | | Even though a vendor APEX sets use_vndk_as_stable:true it was possible to include a VNDK lib by directly depending on it with native_shared_libs. But it's contradictory to have a VNDK lib while declaring not to include VNDK libs. It was missing since pruning dependencies on VNDK libs was done only for transitive deps. Added a check to reject this. Bug: 216847402 Test: m nothing(running soong tests) Change-Id: I8d79a434b1bfe8e563cf8968fa76830b0e582f66
* Merge "Improve apex build check explanation"Treehugger Robot2022-01-201-2/+2
|\
| * Improve apex build check explanationAndrei Onea2022-01-191-2/+2
| | | | | | | | | | | | | | | | | | Discourage jarjaring code where there are alternatives with better system health implications. Test: m Bug: 215233995 Change-Id: I1b076d00e1ad6aa32b41da6bda1033978b5e829d
* | Merge "[NETD-BPF#34] Add a tag for bpf to specify the install folder"Treehugger Robot2022-01-191-1/+8
|\ \
| * | [NETD-BPF#34] Add a tag for bpf to specify the install folderKen Chen2022-01-191-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, the bpf module netd.o (source system/netd/bpf_progs/netd.c) will be built to /system/etc/bpf/netd.o. In Android T, it will be moved to mainline module com.android.tethering. The expected behavior is: - In T device, it uses the netd.o in mainline module. - In pre-T devices, it uses the original netd, built from platform. However, netd.o will be double loaded if the tethering module is installed in Pre-T devices. Because: 1. bpf in apex is packed into /apex/MAINLINE_MODULE/etc/bpf/ 2. bpf in platform is packed into /system/etc/bpf/ 3. bpfloader in pre-T loads ANY bpf modules under /apex/com.android.tethering/etc/bpf/ and /system/etc/bpf/. We can't change the behavior of bpfloader in pre-T devices. We can't delete the /system/etc/bpf/netd.o from pre-T devices. Both of them are not mainline modules. So the mainlined netd.o needs to be packed into a folder other than /apex/com.android.tethering/etc/bpf/ or /system/etc/bpf/. This commit adds a tag 'sub_dir' for bpf module. The installation path of bpf modules will be: - /system/etc/bpf/SUB_DIR/ (for platform code) - /apex/MAINLINE_MODULE/etc/bpf/SUB_DIR/ (for mainline module) Bug: 202086915 Test: add test in apex_test.go and build Change-Id: Icc6619768ab006de9f86620a7df1bb2853eaba13
* | | Allow installing boot images outside of APEX.Jiakai Zhang2022-01-131-0/+16
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After this change, `bootImageConfig.installDirOnDevice` can be set to a path outside of the APEX, in which case, the boot image will not be installed in the APEX. Instead, it will be installed to the given path by Make. This is a no-op change. Current behavior is not affected. Bug: 211973309 Test: m nothing Test: - 1. m com.android.art 2. See the boot image still being installed in the ART APEX. Test: - 1. Change `installDirOnDevice` of the ART boot image config to `system/framework`. 2. See the boot image being installed in `/system/framework/<arch>`. Change-Id: Ib13b17cc9e94dc5754c9b51b04df3307323b8783
* | Add comments and clarify errors in neverallowLiz Kammer2021-12-211-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sample of new error for violation: error: system/bt/gd/rust/topshim/macros/Android.bp:10:1: module "libtopshim_macros" variant "linux_glibc_x86_64": violates neverallow requirements. Not allowed: module types: ["rust_benchmark" "rust_benchmark_host" "rust_binary" "rust_binary_host" "rust_library" "rust_library_dylib" "rust_library_rlib" "rust_ffi" "rust_ffi_shared" "rust_ffi_static" "rust_fuzz" "rust_library_host" "rust_library_host_dylib" "rust_library_host_rlib" "rust_ffi_host" "rust_ffi_host_shared" "rust_ffi_host_static" "rust_proc_macro" "rust_test" "rust_test_host"] EXCEPT in dirs: ["device/google/cuttlefish/" "external/adhd/" "external/crosvm/" "external/libchromeos-rs/" "external/minijail/" "external/rust/" "external/selinux/libselinux/" "external/uwb/" "external/vm_tools/p9/" "frameworks/native/libs/binder/rust/" "frameworks/proto_logging/stats/" "packages/modules/DnsResolver/" "packages/modules/Virtualization/" "prebuilts/rust/" "system/core/libstats/pull_rust/" "system/extras/profcollectd/" "system/extras/simpleperf/" "system/hardware/interfaces/keystore2/" "system/librustutils/" "system/logging/liblog/" "system/logging/rust/" "system/nfc/" "system/security/" "system/tools/aidl/" "tools/security/fuzzing/example_rust_fuzzer/" "tools/security/fuzzing/orphans/" "vendor/"] Old error: error: system/bt/gd/rust/topshim/macros/Android.bp:10:1: module "libtopshim_macros" variant "linux_glibc_x86_64": neverallow -dir:device/google/cuttlefish/* -dir:external/adhd/* -dir:external/crosvm/* -dir:external/libchromeos-rs/* -dir:external/minijail/* -dir:external/rust/* -dir:external/selinux/libselinux/* -dir:external/uwb/* -dir:external/vm_tools/p9/* -dir:frameworks/native/libs/binder/rust/* -dir:frameworks/proto_logging/stats/* -dir:packages/modules/DnsResolver/* -dir:packages/modules/Virtualization/* -dir:prebuilts/rust/* -dir:system/core/libstats/pull_rust/* -dir:system/extras/profcollectd/* -dir:system/extras/simpleperf/* -dir:system/hardware/interfaces/keystore2/* -dir:system/librustutils/* -dir:system/logging/liblog/* -dir:system/logging/rust/* -dir:system/nfc/* -dir:system/security/* -dir:system/tools/aidl/* -dir:tools/security/fuzzing/example_rust_fuzzer/* -dir:tools/security/fuzzing/orphans/* -dir:vendor/* type:"rust_benchmark" type:"rust_benchmark_host type:rust_binary type:rust_binary_host type:rust_library type:rust_library_dylib type:rust_library_rlib type:rust_ffi type:rust_ffi_shared type:rust_ffi_static type:rust_fuzz type:rust_library_host type:rust_library_host_dylib type:rust_library_host_rlib type:rust_ffi_host type:rust_ffi_host_shared type:rust_ffi_host_static type:rust_proc_macro type:rust_test type:rust_test_host Test: go test soong tests Change-Id: I1a7ee6bbc8258dfffa5a76f02c12fb1e54fdba1a
* | Merge changes I8f4eaed1,I358a62d3Jiakai Zhang2021-12-201-1/+1
|\ \ | | | | | | | | | | | | | | | * changes: Dexpreopt standalone system server jars from prebuilts. Dexpreopt standalone system server jars.
| * | Dexpreopt standalone system server jars from prebuilts.Jiakai Zhang2021-12-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds support for dexpreopting standalone system server jars from prebuilts. Bug: 203198541 Test: - 1. Add a standalone system server jar (e.g., by patching aosp/1906158) 2. Build and drop a module SDK and an APEX. 3. Build a system image from prebuilts. 4. See the odex and vdex files generated in $ANDROID_PRODUCT_OUT/system/framework/oat/ Change-Id: I8f4eaed10a1053cd560b8583efa12dc495f58db1
* | | Remove InstallBypassMake and ToMakePathColin Cross2021-12-151-6/+9
|/ / | | | | | | | | | | | | | | InstallBypassMake and ToMakePath are obsolete, remove them. Bug: 204136549 Test: m checkbuild Change-Id: Ie5a6f7254b3d317ed6039e114ed6aec35e1ce273
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-22 14:56:22 +0000