This reverts commit d6777fa812.
Reason for revert: The soong namespaces can be removed after reworking
libfmjni to use select() with filegroups and header libs for qcom/slsi.
Broadcom is not used in any recent shipping device and mtk can continue
using prebuilt for now.
Change-Id: I078b321c7c55c3d7e5cd97e2664208c3d44f513a
The issue of the multi-lined, wrongly expanded LINUX_COMPILER macro is
back (at least for kernel 4.14).
Funnily enough, setting "--hip-path=/dev/null", or using any other file
or directory that exists, would still make clang happy and give a
message stating that it detected HIP anyways:
Found HIP installation: /dev/null, version 3.5.0
To get around this issue, without doing monumental backports and
avoiding warnings from "-Wunused-command-line-argument", set
"HIP_PATH=none", where "none" simply indicates a non-existing
file/directory.
Change-Id: Ia97d69425716d28208ba344bde79a910e5f75c84
Signed-off-by: voidanix <voidanix@keyedlimepie.org>
It was caused by package-cache in case Build.VERSION.INCREMENTAL
doesn't change across builds, which is always the case for local
builds, exporting BUILD_NUMBER to something != eng.$USER will fix
it the next build.
Change-Id: Ic602197e6711ced511a0b102b1140c5db4ec8397
This reverts commit 2baeb4fb8b.
CPATH is used for both host and target. Meaning that system headers
will be used for target compilation. It is also a higher priority than
isystem, which is used for the compiler include paths, making this
override the compiler headers.
Change-Id: I4d836698f25d2d97d917d323a22ee359b937fcb4
Starting with android common kernel 6.6, rust is enabled for arm64 gki.
It currently looks for rust version 1.73.0, so that was selected as the
default. This was only added for the clang compile path as gki requires
clang.
Change-Id: Ie7b57568d74cfb4a28a94c8dc8f4b5c622044317
Book-style foldables like the Pixel Fold, Galaxy Z Fold and Xiaomi MIX
Fold series have two displays: one primary, near tablet-sized inner
panel and a smaller, phone-sized outer panel.
These devices need a combination of configs to enable both phone- and
tablet-targeted features. Therefore, add a config file merging contents
of the common phone and tablet configs.
Change-Id: Ibf89e4336fa119ebfb79aad8dac4266fd4972985
Signed-off-by: Jens Reidel <adrian@travitia.xyz>
* When the boot image is modified, recovery updating fails because the patch no longer applies to the modified boot image, so ship a full recovery image instead of a patch so recovery updating always works.
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
Change-Id: I56cf6c4d301afa88b39b31d488c5166903406637
Reserving 8MB does not guarantee that free blocks will be >= 1%, so not
only this doesn't work properly, but also breaks builds for some
devices.
This reverts commit 3940fb4240.
Test: breakfast kebab && WITH_GMS=true m
Change-Id: I330570dc6fc9efca5629358a0b149f131d36ba18
This reverts commit bc8d7739ac.
Reason for revert: no longer needed when using blobs that match tag
DISPLAY.LA.3.0.r1-10700-KAILUA.0.
Change-Id: Ia89ce566a4cade6091a2dc6bc4e8b56ef7d1f73b
* When we remount partitions via `adb remount`, a scratch partition
is made for overlayfs to use - this takes up space and breaks OTA.
The end user /could/ run this to fix it:
`adb reboot fastboot && fastboot delete-logical-partition scratch && fastboot reboot`
But that's bad UX, remount should work. This ensures that with or without GMS,
we reserve some space on all dynamic partitions.
* Set amount to `8 * 1024 * 1024` + 1 for good measure.
* Don't reserve this amount of `-user` builds as we don't remount
there.
Change-Id: I969aea92747a17ceca299e109c6e0ab563951374