| commit | 41b64550d8009f81c821439d286a30933a3bfc7b | [log] [tgz] |
|---|---|---|
| author | Michael Wright <michaelwr@google.com> | Thu Jul 18 20:36:10 2024 +0000 |
| committer | Android Build Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Thu Jul 18 20:36:10 2024 +0000 |
| tree | 5986e4fcc9a4f6524156775f17ba462f70dcbd92 | |
| parent | 726c69d608130b9e4b4871e47953d4f03f4f40f8 [diff] |
Pass the target product to release-config
If you don't, release-config will read the TARGET_PRODUCT environment
variable to determine the product. This works in most cases, but it's
possible (e.g. via buildspec.mk) to change the target product within
make without modifying the environment variable. In these cases,
release-config will produce the config for one product but then the
build will read the config for a completely different product, leading
to build errors.
Instead, just pass the target product to release-config explicitly so it
generates the config for the product that the build is expecting.
Bug: 353351911
Test: TARGET_SKIP_OTA_PACKAGE="true" build/soong/soong_ui.bash \
--make-mode TARGET_PRODUCT=apps TARGET_RELEASE=next \
TARGET_BUILD_VARIANT=user droid dist \
ANDROID_BUILDSPEC=vendor/google_clockwork/build/app_build_spec.mk \
ALLOW_MISSING_DEPENDENCIES=true \
UNBUNDLED_BUILD_SDKS_FROM_SOURCE=true \
RELAX_USES_LIBRARY_CHECK=true
Flag: EXEMPT bugfix
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:310d7718439d074fe38b25b97eb609f6db66c3d6)
Merged-In: I63e80249ac702b5517f4a3cfd54c8a4dbd416794
Change-Id: I63e80249ac702b5517f4a3cfd54c8a4dbd416794
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.