commit | 42230120992afdd4584e9ef23cb8ce30a8d782a6 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Thu Jul 19 10:11:10 2018 -0700 |
committer | Tao Bao <tbao@google.com> | Thu Jul 19 10:16:45 2018 -0700 |
tree | 981fce543a34db3db7b7087351177d78f3bfe053 | |
parent | 25e4495de179eb606ab756de5783dbd9d81dac5b [diff] |
releasetools: Remove the assertion of not allowing thumbprint in Treble world. The claim in the original CL doesn't seem to hold. We may still have devices using both of thumbprint and Treble compatibility check. Bug: 111640956 Test; python -m unittest test_ota_from_target_files Test: Build an incremental package for a target using thumbprints. Change-Id: Ia491d5279901c2385d1c30802abcb99d65d919cc
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.