By default, the version control information isn't checked to save time.
The normal version check uses repo, which is blocked by the aosp build
system. So the manifest is generated separately and passed to bazel.
Change-Id: I2232903af6b6b7869aef3f66d836236a041887cc
This was originally verified against out-of-tree, which is already an
absolute path. With in-tree out, the path is relative. Since pwd is
changed to the root of the kernel platform tree, the dist path needs to
be absolute.
Fixes: 7cd90ecd (kernel: Support building from kernel platform)
Change-Id: Ib9cecdc5f8bfd3345afc73c050ab6214ac4c48d6
In the interest of customization, here are a bunch more alarms and notifications sounds. The code is taken from ProtonAOSP, and adapted to Lineage.
Cherry-picked from: 629b35007c
Cherry-picked from: 6f203a966f
Change-Id: Iaacb0d2e94d2dda1cf90cabb9368cea1a4cf0a7f
Authored-by: Danny Lin <danny@kdrag0n.dev>
Co-Authored-by: Inhishonor <inhishonor@protonmail.com>
This expects a few build variables to be set:
* TARGET_KERNEL_PLATFORM_TARGET: The base target name. For example,
'tegra' will indicate that the dist target is tegra_dist, abi is
tegra_abi, etc.
* TARGET_KERNEL_VERSION: Used to determine the kernel checkout path. For
example, a value of 6.6 will expect the kernel platform repo to be
checked out to $BUILD_TOP/../kernel-6.6.
* TARGET_KERNEL_SOURCE: Relative to the top of the kernel platform
checkout, the path to the kernel build rules. For example,
vendor/nvidia/tegra.
* BOARD_KERNEL_IMAGE_NAME: The kernel image to use. For example, Image.
Using the examples above, this will run bazel in the kernel-6.6
directory on the target //vendor/nvidia/tegra:tegra_dist, then source
the output from $OUT/tegra/dist, with the prebuilt kernel image being
Image.
Change-Id: If96e96dffa2c0bfd9bd824bb3d8064eb861c9d00
