| commit | ae5e4c30fea6ab944d303d4a5a2621c10a926f95 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Mar 01 19:30:00 2018 -0800 |
| committer | Tao Bao <tbao@google.com> | Thu Mar 08 14:59:42 2018 -0800 |
| tree | 2e02d429879177943617538885551a861bd3afa0 | |
| parent | b5399007ca4f141123d3a668f904a1c83a5dec58 [diff] |
releasetools: Create StreamingPropertyFiles class. This CL breaks down ComputeStreamingMetadata() into mutiple member functions of StreamingPropertyFiles class, which correspond to the two-pass logic when generating streaming property files (aka streaming metadata). StreamingPropertyFiles.Compute() does the work for the first pass, by putting placeholders before doing initial signing. Finalize() corresponds to the second pass, where the placeholders get replaced with actual data. Verify() can be optionally called to assert the correctness of the work. The separation between Compute() and Finalize() is to allow having multiple StreamingPropertyFiles instances (in coming up CLs). This way we can call Compute() multiple times for each instance, followed by only one call to SignOutput(). And similarly for Finalize(). Bug: 74210298 Test: Generate an A/B OTA package. Check the METADATA entry. Test: python -m unittest test_ota_from_target_files Change-Id: I45be0372a4863c4405e6d8e20bcb9ccdc29e7e11
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.