Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 6f488e9e339956914d3d7b3295949a0f9e52bfbf
commit6f488e9e339956914d3d7b3295949a0f9e52bfbf[log] [tgz]
authorTJ Rhoades <tjr@microsoft.com>Sun May 01 22:16:22 2022 -0700
committerTJ Rhoades <tjr@microsoft.com>Mon May 02 13:19:49 2022 -0700
treea5388f9193627c1a4b90278b1eb98b3d9d858a70
parentd3eb2e30dc5e5551ae4a0e4837f14fca0c31dbd3 [diff]
Expose GetRamdiskFormat and use in ota_utils.py

Some OTA files may have additional OTA props; when this is being computed within
ota_utils.py -> ComputeRuntimeBuildInfos, the ramdisk type needs to be passed into
PartitionBuildProps.FromInputFile as not all ramdisk may still use gzip. This check
is already defined in common.py, so this change also exposes the function GetRamdiskFormat.

Bug: 231075507

Signed-off-by: TJ Rhoades <tjr@microsoft.com>
Change-Id: If1b93b887990f0d90df2c6003122821c1e66a1ac
2 files changed
tree: a5388f9193627c1a4b90278b1eb98b3d9d858a70
  1. common/
  2. core/
  3. orchestrator/
  4. packaging/
  5. target/
  6. tests/
  7. tools/
  8. .gitignore
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. finalize_branch_for_release.sh
  16. help.sh
  17. METADATA
  18. navbar.md
  19. OWNERS
  20. PREUPLOAD.cfg
  21. rbesetup.sh
  22. README.md
  23. tapasHelp.sh
  24. 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.