Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / 491d7e2ea8bac77ad20b40f9faf10e1fb2cc7075
commit491d7e2ea8bac77ad20b40f9faf10e1fb2cc7075[log] [tgz]
authorTao Bao <tbao@google.com>Wed Feb 21 13:17:22 2018 -0800
committerTao Bao <tbao@google.com>Mon Mar 19 14:53:10 2018 -0700
tree9574eefb5785fb8380a8b693b724f949a2450a21
parentdc3806d97ea9933c5ec6627635973116fef5cdca [diff]
releasetools: Add NonAbOtaPropertyFiles for non-A/B OTA packages.

This CL exposes ota-property-files flag for non-A/B OTA packages.
Currently the line only contains the info for the METADATA entry, for
example "ota-property-files=metadata:69:286". This allows system updater
to just download the METADATA entry, as opposed to downloading the
entire package, to learn about the info regarding the OTA package (e.g.
post-OTA build fingerprint). Note that this requires the OTA server-side
support to pass down the flag along with the update URL.

Bug: 74210298
Test: python -m unittest test_ota_from_target_files
Test: Generate a non-A/B package and check the property-files string.
Change-Id: I1482c587e18ea7101c8328777ea988c2d8ca06ac
Merged-In: I1482c587e18ea7101c8328777ea988c2d8ca06ac
(cherry picked from commit c0746f4e944981a944349bc4645b546a47eb9e58)
2 files changed
tree: 9574eefb5785fb8380a8b693b724f949a2450a21
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. Usage.txt
README.md

Android Make Build System

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.