mkfs warns about unknown "selabel=" fields, and this should be coming
from the file_contexts file, not here.
Test: treehugger
Change-Id: I63f3f616a2588438017e609a1a08c9dd7bf0c2ed
Introduces ide_query_cc_analyzer, which figures out relevant build targets that needs to be built for a given C++ source or header file.
Once these targets are built, it analyzes the sources in question and reports any generated files that are used back.
Full ide_query integration relies on this binary also being available in prebuilts clang-tools, it'll be done in a future patch.
Change-Id: Ib0ef6da7a2bc8ecf66940b326e037fb1ee230bf9
This silences warnings such as:
linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt"
WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt"
that are printed at the start of every command in the first
stage console.
Change-Id: I3d820e4960a4dbca34369223aed83589534c2eb6
This product is an extension of the sdk product, and allows the
"runtime" api stub artifacts are exported to the dist directory and used
to generate the stubs.
Test: lunch sdk_with_runtime_apis-trunk_staging-eng && m sdk dist
Bug: 326312949
Change-Id: I96f6c1f5a5e7b40165d55ea4c0898a880ed62c96
PRODUCT_EXPORT_RUNTIME_APIS is a product variable that inherits the
behavior of the build flag RELEASE_EXPORT_RUNTIME_APIS, which is being
removed. This will be utilized in the product `sdk_with_runtime_apis`,
which will be introduced in a future change.
Test: m nothing --no-skip-soong-tests
Bug: 326312949
Change-Id: I4966b7bfc7423db049acfcede67233352ba8341b
The new product variable behaves identical to the build flag
RELEASE_HIDDEN_API_EXPORTABLE_STUBS: if the variable is set to true, the
hiddenapi flags are generated from the "exportable" stubs (i.e. the
stubs that does not include READ_WRITE permission or DISABLE state
flagged apis) instead of the "everything" stubs (i.e. the stubs that
includes all flagged apis regardless of the state of the flags). If the
variable is set to false, the stubs are generated from the "everything"
stubs.
This product variable will be utilized for `sdk_with_runtime_apis`
product in the future changes.
Test: m nothing
Bug: 326310637
Change-Id: Iab3b46ac39972b8721d3aa07cec622c57dafbd0e
Otherwise system_ext.img wouldn't be built under $PRODUCT_OUT dir when
building a system.img&system_ext.img only build target.
Bug: 326359088
Test: Build a system/system_ext image only target
Change-Id: I8732f7a578350f8bc3b91f8a1db656bf95eddc95
There's no point testing the system vintf boundary on a system image
-less target.
Bug: 326354182
Bug: 326359088
Test: Build a system image -less target
Change-Id: I1ef71f93acb1e7a6252ae14e18c30cb23cb08db2
Right now write-file-lines is defined only if BUILDING_SYSTEM_IMAGE is
true. This means split build / partial build targets that doesn't build
the system image, would fail to build other partition images too
because the $(<parttition>image_intermediates)/file_list.txt build rule
would be undefined.
Move the macro definition out of the `ifdef BUILDING_SYSTEM_IMAGE`
conditional block.
Bug: 326359088
Test: build a target that doesn't build system image
Change-Id: I020c28f7011bd0df0330ba3350e50bea2b75aab4
Adding 256k support for ota_from_target_files since this is the max
comperssion_factor allowed in v3 cow
Test: ota_from_target_files
Change-Id: Ic7826c82e53ec3fdbd04fdff9dfb7a76038f6a42
Add a new CLI binary that we can use as the officially recommended CLI
for reading and writing flags. For now, the CLI invokes commands to
interact with DeviceConfig and aconfig protos, but we will switch it to
interact with the forthcoming mmap-file-based aconfig storage. In the
meantime, we can add improved formatting and error reporting in a
separate layer.
This CL starts with the list command, which outputs a table of the
flags when you type `adb shell aflags list`.
Bug: 324436145
Test: atest aflags.test
Change-Id: Idd8aa78ccaace22a7e490014d410ad741f8f6fc6
Files need to be moved from platform to the new apex.
Adding a flag to control this movement.
More Details: go/conditionally-move-android-files
Bug: b/289203818
Test: m
Change-Id: Id3674bd6a8a32f64d189b8ac17b222b9d7966f69
Merged-In: Id3674bd6a8a32f64d189b8ac17b222b9d7966f69
We have more known codenames then we are releasing, and need a way to
override this in release configs.
Bug: 307733231
Test: m nothing
Change-Id: I2215dc449ca28cae253f514183507550b58f267b
Merged-In: I2215dc449ca28cae253f514183507550b58f267b
(cherry picked from commit 569b9e08fa)
- Define findlsdumps_LLNDK that vFRC process will build.
- Move LSDUMP_PATHS_FILE to target/product/gsi/Android.mk.
- Allow LLNDK dumps in prebuilts/abi-dumps/vndk.
Test: m findlsdumps_LLNDK check-vndk-list
Bug: 314010764
Change-Id: I6329cd4b1b919069291a13bd03720ceea46b95ff
Build general-tests_configs.zip and general-testlist.zip as part of the
build_test_suites step, which general-tests also outputs.
Test: BUILD_NUMBER="P0" ./build/make/ci/build_test_suites --target_product aosp_x86_64
--target_release trunk_staging --with_dexpreopt_boot_img_and_system_server_only --dist_dir <dist_dir> --change_info <change_info_file> <extra_targets>
Bug: 314171817
Change-Id: Ic324ed4e5a05e1308dee3af7f15c067f88018b2d
Split out the building of the host shared libs zip from the
general-tests target so it can be built separately. building
general-tests will still build both.
Test: m general-tests, m general-tests-shared-libs
Bug: 314171817
Change-Id: I99f6d7ae5578d8bc97ddc0c047398defbf9b8cc9
SDK library for pdf related bootclasspath classes that were part of the non-updatable API before V, and were moved to the module in V. Other pdf related bootclasspath classes in mediaprovider should go to framework-pdf.
Bug: b/324667310
Test: presubmit and m
Change-Id: I92aabf297508f2c885a721d11d40b5262b6847fe