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
Kernel 6.6 is not currently set up for CONFIG_NETFILTER_XTABLES_COMPAT,
breaking 32-bit iptables userspace.
Change-Id: I79823ea1c66d841f204a1d3c241619abb51f9040
Some devices have the same codename but shipped a long time
ago and may not have a current branch set up.
Continue looking up all repositories until a match is found
or no repos are left to check.
For example:
- android_device_amazon_thor
- cm-14.1
- android_device_xiaomi_thor
- lineage-21.0
- android_device_semc_zeus
- jellybean
- android_device_xiaomi_zeus
- lineage-21.0
- android_device_amazon_otter
- cm-12.1
- android_device_shift_otter
- lineage-21.0
Change-Id: Icf9826b31efd872363fdfe73d5a71ff2d06cbe20
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
Revert "kernel: Check HIP support of clang before disabling it"
This reverts commit 62c1374385.
Revert "kernel: Force disable LLVM HIP"
This reverts commit ef68678120.
Revert "kernel: Force disable LLVM CUDA"
This reverts commit ba14020f85.
Change-Id: I5cb2b4624eb0ec25dbc8c1b5888708d961ae59d7
Since ADDITIONAL_SYSTEM_PROPERTIES is being deprecated, this will
need to be handled in build/make and build/soong
Change-Id: Ib4925969f0d9f60ea5b30455806ff80a1817d61f
This target just builds the `.config` in
`KERNEL_OBJ`/`RECOVERY_KERNEL_OBJ` to quickly check if fragments are
applied properly, not to be used during an actual kernel build
Change-Id: Ic92fe7bd544f6d0f1b3169c1405aceb6702775e0
write() handles XML conversion and file writing internally.
The xml_declaration=True parameter adds the XML header
automatically, eliminating the need for manual string manipulation
Change-Id: Ib8c3fe33e60accad05572c5af0f0b90866a219d9
Signed-off-by: Jyotiraditya Panda <jyotiraditya@aospa.co>
Change I8b6040e03589bde2af4e161c891ded237a9bb335 did not account for
devices without a separate vendor partition, causing build to fail with
the following:
FAILED: ninja: '/file_list.txt', needed by 'out/target/product/joan/obj/KERNEL_OBJ/arch/arm64/boot/Image.gz-dtb', missing and no known rule to make it
Use systemimage_intermediates instead on said devices.
Test: m kernel
Co-authored-by: Bruno Martins <bgcngm@gmail.com>
Change-Id: If9eb75a1bef98345e9c137c2463e392d50be239b
- Mention the right kernel image on documentation
- Build dtbs only when the dts folder exists, Google enables CONFIG_OF
on x86_64 GKI config, this is also the same check done on Linux
Makefile
Change-Id: I1b0f7a39b0b00f2a4516d2cff79e591136ee3af8
This is required to ensure that kernel modules end up on the final
partition images when `BUILD_BROKEN_INCORRECT_PARTITION_IMAGES`
environment variable or board config variable is not set.
See 152cdfab7c
for more information.
Co-authored-by: Bruno Martins <bgcngm@gmail.com>
Change-Id: I8b6040e03589bde2af4e161c891ded237a9bb335
QPR2 introduced remaining build time in the progress box [0]
but it was broken with tee cmd so dopush() was worked fine.
Now, QPR3 fixed that issue so dopush() is broken.
Example:
[ 99% 394/395 1m30s remaining] Copy: out/target/product/devon/apex/art_boot_images/javalib/arm/boot.art
[100% 395/395 1m30s remaining] Install: out/target/product/devon/system/framework/framework.jar
Change-Id: Ifdfcfe0f750d39f4e3fe7d669e5094729d75e224
* Bypasses the literally infinite timeout for users who have
limited access to GitHub (before: 2m13.749s, after: 0m14.354s)
* The timeouts should be enough for users who have freedom internet
access, even ADSL network connection shouldn't take that long...
Test:
1. Execute `source build/envsetup.sh`
2. `breakfast` a existing device
3. Add "0.0.0.1 github.com" and "0.0.0.1 raw.githubusercontent.com"
to /etc/hosts
4. `breakfast` any device, observe that it should not take up to
minutes to quit
Change-Id: Ib90e69c75a50e66b47e6245cb6d0521351b5c71b
Some OEMs (for example: oplus) push their dtbs to their own folders which causes kernel build to error out, fix this by including non qcom dtbs as well.
Change-Id: I2f51db103475cd2609cd061e0ec66af5accb96ab
This can happen when an out of tree module target uses a matching module
name from the base kernel. This causes two problems:
1) Depmod gets confused and only pulls symbols from one of the modules
2) Copying the modules to modules_out is not entirely deterministic and
is based on the first variant to be returned by find, meaning that
the variant that gets copied to the device could change build to
build.
To avoid these issues, fail the build if this happens and force the
build target to only generate one copy of each module name.
Change-Id: I2e47ba4e142054feabaa1ab80fbbe0332fd84a62
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
Build is now a group instead of a repo.
The actual repo got renamed to build_repo.
Change-Id: I61f65251896d18c3025d849109206d44e2686c70
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
Original commit incorrectly added kernel as a dep to the vendor ramdisk
for this path, when instead the dep should be added to the boot ramdisk.
Change-Id: I25a42d403fe2ddb0538b08c2dd8f761eae960810
With the merge of tag 'android-14.0.0_r29', the emulator sdk_phone_x86_64
is inherited from device/generic/goldfish. This means, that the component
PRODUCT_SDK_ADDON_COPY_FILES needs to be defined here.
Change-Id: I2cee21d27f28521f34e80262c2abda6b7eb3360c
With the merge of tag 'android-14.0.0_r29', the emulator sdk_phone_x86_64
is inherited from device/generic/goldfish. Its defined super partition
size of 1.6GB however is too small to build the LineageOS 21 emulator.
Therefore, overwrite the partition sizes with the values as previously
set in build/make/target/board/BoardConfigEmuCommon.mk
Change-Id: Ib8443cb3d8cacb42cab68f154845574fadf99b55
necessary after merge of tag 'android-14.0.0_r29':
e04167e Retire obsolete (32bit-only) emulator targets and boards
Please use 64bit-only targets instead:
[...] * we don't support x86+arm for AOSP targets
Change-Id: I001b97e218f837005d4283bd0540519b00301783
necessary after merge of tag 'android-14.0.0_r29':
228de7b Remove sdk_<arch> products
The SDK is arch-agnostic, so does not need per-arch products.
Change-Id: Idac94e841e749d6dcc4aa643b8738f8c07ac71fa
necessary after merge of tag 'android-14.0.0_r29':
4bf479f Retire obsolete emulator targets and boards
the sdk_phone* targets are replaced with sdk_phone64*,
the emulator* boards are replaced with emu64* in
the device/generic/goldfish folder.
Change-Id: Ie36e73684d586223bbce642a62cf155a3990713e