| commit | 35dc255180d2d84be7fdc86a3eecff05c33937d0 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Feb 01 13:18:00 2018 -0800 |
| committer | Tao Bao <tbao@google.com> | Thu Feb 01 15:58:20 2018 -0800 |
| tree | 469ff136645fd1b8fbf22ab15e05a2eb2d9f165b | |
| parent | a4c7d59afca1e74309ba5292cf8fe3d51773665b [diff] |
releasetools: Add sdk and security patch level info to metadata. The info comes from the build.prop file of the target build (thus no backward compatibility concerns). OTA server and client can optionally use these info to understand the expected behavior of an OTA package. Bug: 72751683 Test: python -m unittest test_ota_from_target_files Test: `m dist`, then check the metadata in the generated OTA package. Change-Id: I5935f67684d2486bb5f00d67ce4bc756589a56ed
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.