| commit | c0fde810bae2bb2f4b286a7a2bd7aeb826ad9951 | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Tue Sep 28 20:01:50 2021 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Fri Oct 15 15:39:28 2021 -0700 |
| tree | cadb3dbb69e22a8924e7c2522a279945b2b1d0f2 | |
| parent | c5d5bb424f504d9558495692a776742b53024908 [diff] |
Provide is-vendor-board-qcom macro. `is-vendor-board-qcom` supplants `is-vendor-board-platform` as the latter's second operand is always `QCOM`. To check that BOARD is a QCOM one, write: ``` ifneq (,$(call is-vendor-board-qcom,BOARD)) ``` Using `is-vendor-board-qcom` before its implied operands `TARGET_BOARD_PLATFORM` and `QCOM_BOARD_PLATFORMS` are set is an error. Bug: 201477826 Test: treehugger Change-Id: Ie7063c46b7eda092438a59f3682486dd39af3d0b
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.