commit | c8c516a89ba8ff008515d381e93bee68611d2d68 | [log] [tgz] |
---|---|---|
author | Cole Faust <colefaust@google.com> | Thu Dec 09 10:30:19 2021 -0800 |
committer | Cole Faust <colefaust@google.com> | Thu Dec 09 10:30:19 2021 -0800 |
tree | 7d86573d6070dda52e5f13342c9661f6d213fe0a | |
parent | 1295bc51383913eddfa76fb2f9c6e22cac102a4b [diff] |
Strip ODM_MANIFEST_SKUS Otherwise it gets a different value when using starlark board config, causing the ninja files to differ. Bug: 201700692 Test: ./build/bazel/ci/rbc_regression_test.sh -b aosp_crosshatch_car-userdebug Change-Id: I55870f031b779202db720f10d7d502f9d868e1f6
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.