So far, we have *_system.mk and *_vendor.mk.
This patch split all product settings from *_vendor.mk to new
*_product.mk
This patch also create a new telephony.mk to include all
telephony_*.mk
Bug: 119747870
Test: lunch mainline_arm64-user; make -j
Test: compare the content with and without the patch
Test: the output files in out folder are the same
Change-Id: I79aefdd1971b3b5724a3ec858de4109b645c765a
Merged-In: I79aefdd1971b3b5724a3ec858de4109b645c765a
This product variable is used to generate the loader config (to use
either /system/product or /product), and the vendor one is likely
used in similar ways. Having these partitions is required for mainline
devices, so set it in the shared BoardConfig.
Bug: 80410283
Test: make
Change-Id: I6f2d94ff43572a28df54ea8c60f2d838a3b9216c
The app will move to product soon, but temporarily
whitelist that mainline_arm64 adds it to /system.
Test: make
Change-Id: I7b0ce5623a160bcb0f8b89f3053a007019ff0b62
It is present in media_vendor.mk (and soon media_product.mk),
which is the correct place.
Test: make
Change-Id: I7ffda211cf4b01a22ec01c661959defcf59bbc4b
The Android Runtime APEX is always included on all products.
Test: make systemimage on marlin-userdebug
Test: make systemimage on sailfish-userdebug
Bug: 113373927
Change-Id: I47b02ee44562b8da17bd960825a3489572018d93
Rename ANS to ONS
Bug: 118347827
Test: compile
Merged-In: Id01f0fc595e736f081d97309f62426cc54ac9e94
Change-Id: Id01f0fc595e736f081d97309f62426cc54ac9e94
Bionic libs are moved to the runtime APEX and thus are available via the
path /apex/com.android.runtime/lib[64]. However, for processes that are
started before the APEX is ready, a copy of the bionic libs should be left
under /system/lib[64]. This change ensures that the bootstrap bionic
libs are always installed to the system partition.
Note that, at runtime, the bionic libs in the runtime APEX are
bind-mounted to /system/lib/<libname>.so which essentially hides the
bootstrap bionic libs to the processes after the activation of the
runtime APEX.
Bug: 120266448
Test: m and check that libc, libdl, libm are under
/system/lib[64]
Change-Id: I9d5e8e718aa020c012f312a70ed54652130048dd
It's 2019 and the CDD has required NEON for many years now.
I've left unbundled apps alone for now.
I think the recent fix here for https://issuetracker.google.com/116070933
was incorrect. (I've commented on the bug.)
Test: treehugger
Change-Id: Ia02305cfdff9fd18a85359bc44d8eb9cab1413bd
Individual products can add their own calculator package if desired.
Bug: 120905067
Test: lunch aosp_arm64 && make -j8
Merged-In: I60490b6e2a42c4304768075e8fef9f07cb72d268
Change-Id: I60490b6e2a42c4304768075e8fef9f07cb72d268
Legacy GSI had been changed to include BoardConfigGsiCommon.mk
instead of treble_common*.mk. However, some default settings are
different than the original. This patch fixes
BOARD_BUILD_SYSTEM_ROOT_IMAGE in Legacy GSI makefiles.
The patch also removes redundant settings and fix some comments.
Bug: 122282239
Test: make
Change-Id: Ie4eb8cf410bfd2edc74648c0e5ee81028242a1b7
It's 2019 and the CDD has required NEON for many years now.
I've left unbundled apps alone for now.
Test: treehugger
Change-Id: Iee22d4605a81e2840063a203b76db7df5b4f3c37
Generate and store minimum amount of information necessary to
create backtraces in native tools (for crashes and profilers).
The data is compressed and takes <5% relative to JIT code size
(which is less than recent stack map savings; so win overall).
Averages for non-compiled run of maps which filled JIT code cache to ~4MB:
Q: code:1.55kb/method data:0.738kb/method debug:0.064kb/method(*this CL*)
P: code:1.62kb/method data:0.956kb/method debug:0.835kb/method(if enabled)
I also measured the P to Q on-disk stack maps savings in CL/762841 as ~28%
(not all of that is applicable to JITed code, so that is an overestimate).
Bug: 111350693
Test: Device boots, mini-debug-info is generated.
Change-Id: I95883bd4f2d5c2308149ab0ba641b0a703c7f81b
All these modules are to be moved to /product, as they are not
part of the core system image. Move them out of the _system mks
as a start, and temporarily whitelist them so that they can be
moved iteratively.
Bug: 122353713
Test: make
Change-Id: If658e6b4565924cd915a183400c5b2b32984eca4
Merged-In: If658e6b4565924cd915a183400c5b2b32984eca4
The patch modifies the Legacy GSI to use BoardConfigGsiCommon.mk
instead of board config treble-common*.mk, and delete these
treble-common*.mk files.
After the patch, the GSI common board configs are in single file
BoardConfigGsiCommon.mk
The patch also includes:
- Moving `TARGET_COPY_OUT_VENDOR := vendor` to
BoardConfigGsiCommon.mk, because GSI always contains no vendor
contents.
- Configure the binder interface bitness explicitly.
- Unify the structure of each BoardConfig.mk.
Bug: 122282239
Test: compare the out folder between with and without the patch
Test: output files are all the same
Change-Id: Ie5901446920dda317dea848e6d5a7bbcf10a32cf
Contains mainline_system and the relevant AOSP packages for the
other partitions. Intended to be inherited by the aosp_X variants
of mainline devices.
Bug: 118826166
Test: build mainline_arm64
Change-Id: I7d1953bf5ccda4d9652dca4d32efb75b31015342
Similar to I1720644d89ec5289fbe99f95ebcdfbb3f3b20e67,
but for mainline_system. This reduces the diff between
full_base.mk and mainline_system, a step on the way to
get aosp_blueline inheriting mainline_system.
Bug: 118826166
Test: make
Change-Id: I52bfe5dfb3e1a22db2d46fe9d1f372ee25533fdd
The binder interface bitness is always 64bits from P.
To keep 32bits binder interface for Legacy GSI, we need to explict
configure it.
Bug: 122282239
Test: lunch aosp_arm_ab-userdebug; make -j
Change-Id: I90b45adb52c398d1c0cf3f877199f9dd1e0b3f86
soong_ui is passing the Android.mk file list to Kati, and it ignores
Android.mk files found via symlinks, so we don't need the workarounds
for build/make/target/board/Android.mk and build/target/board/Android.mk
both existing.
We've got dist support in Soong now, so we can remove the signapk
Android.mk
Bug: 122332221
Test: m dist out/dist/signapk.jar out/dist/libconscrypt_openjdk_jni.so
Change-Id: I2ac9016b04146340c5ac80f7090d00e186023574
dmctl can list all device mapper targets and their tables which is
extremely useful information for a bugreport. Especially to compare
the device mapper setup with the partition metadata.
Bug: 120916687
Test: 'dmctl list device -v'
Change-Id: I9e3afcf146b2814b0304f69cdf6029303beb57c7
Merged-In: I9e3afcf146b2814b0304f69cdf6029303beb57c7
Signed-off-by: Sandeep Patil <sspatil@google.com>
Home is overriden by Launcher3QuickStep, so listing these two
in the same mk is a noop.
Test: make
Change-Id: I2865a5346c63efd78e434185041f320ca344e854
