Devices that shipped on API 33 or higher need to set
ro.product.first_api_level to 32 in order to pass integrity.
Set SPOOF_FIRST_API_LEVEL_32 := true in BoardConfig*.mk to enable.
Signed-off-by: AnierinB <anierin@evolution-x.org>
Original command redirected output to the android build out. However, a
handful of configs were still generated in the source tree. Set the
bazel flag output_root to redirect these configs to the android build
out as well.
Change-Id: I5181270b773a49d74eab00b89eaaf1187471a144
Devices that shipped on API 33 or higher need to set
ro.product.first_api_level to 32 in order to pass integrity.
Set SPOOF_FIRST_API_LEVEL_32 := true in BoardConfig*.mk to enable.
Signed-off-by: AnierinB <anierin@evolution-x.org>
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
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
This has been unused for a long time and any users that mistakenly use
this should migrate to defconfig fragments.
Change-Id: I70f1aa82e3adcbf85b11e8685f188d0eadfff2e3
... but sets SYSTEM_KERNEL_MODULES
build/make lets BOARD_SYSTEM_KERNEL_MODULES_LOAD default to false
when it's unset.
Change-Id: I581da33bf0321f171aa6a20bdb023e1ee824cb18
For targets that uses mainline kernel, the kernel tree usually only
contains configs on top of the upstream repository.
In such case, if we put the configs in elsewhere, we can simply just
track the upstream kernel repo, without needing to import configs.
Example usage:
TARGET_KERNEL_CONFIG_EXT := \
$(COMMON_PATH)/kconfig/platform_defconfig \
$(COMMON_PATH)/kconfig/common-addons.config
TARGET_KERNEL_CONFIG_EXT += \
$(DEVICE_PATH)/kconfig/device.config
Change-Id: Ibafd0afa7ec06df643ba290a6149a4f0781d67fb
* Allow wildcard pattern
* Support searching in specified directory
* Add variable that accepts a list of such patterns
Change-Id: I35da8ed19447b4ab69142152d7dc8e60bc55bf14
It has been noticed that sm8750 no longer puts GKI modules in the
subdirectory. Moreover, this seems to be something specific to QCOM,
so guard it as such.
Change-Id: Iac9c895c9c1eef06b2e4ce75bd7c5c2aa356fbb1
Currently there is a limit of 500 changes per page, giving us only
those when repopicking a query. By observing the "_more_changes" field
in the response and adding the "start" parameter to the query we can
do pagination and return all changes
Test: repopick -p -Q "branch:lineage-23.0"
Result before: 500 changes
Result after: 1094 changes (correct count as of time of commit)
Change-Id: I00304bc2c87b75cef89a26838da3dd1b1f0e65db
Needed for KERNEL_CLANG_VERSION if TARGET_KERNEL_CLANG_VERSION hasn't been set by the device config
It's boring to change it on each Google change ...
Change-Id: I1d682611cbf6c60d7ae6227b0b5afde591adf471
