Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 4c0faf0110a6fd8abb768f2a438b2d59bc44fb00
commit4c0faf0110a6fd8abb768f2a438b2d59bc44fb00[log] [tgz]
authorHerbert Xue <herbertxue@google.com>Tue Mar 18 14:56:15 2025 +0800
committerHerbert Xue <herbertxue@google.com>Wed Mar 19 17:10:37 2025 +0800
treece99d41e0c13d51b84305b84bff4d3305c8c2ba5
parent4895bb75fd3b51547404af1dee29429be0a57e92 [diff]
Convert the otatools.zip to soong for jars, cert files and releasetools

- Use "otatools_package_cert_files" to find cert files.
- The jar modules is from $(INTERNAL_OTATOOLS_MODULES_WITH_DEPS).
- The "otatools-package-temp" is temporary. It will be changed as
  "otatools-package" after all files are ready in soong.

Bug: 395988167
Test: m dist otatools-package-temp
Change-Id: I473457cbd343473bdbc21874a18565aadd9d37a0
2 files changed
tree: ce99d41e0c13d51b84305b84bff4d3305c8c2ba5
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.