Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / c34c3738ba6be7ef1fc3acb7be5122bede415789
commitc34c3738ba6be7ef1fc3acb7be5122bede415789[log] [tgz]
authorLuca Farsi <lucafarsi@google.com>Wed Mar 12 22:19:00 2025 +0000
committerLuca Farsi <lucafarsi@google.com>Wed Mar 12 22:19:00 2025 +0000
treeb056e94a7943a9187553bc56e27f0f841d16efa4
parenta351519bd28b3c375657687edb80eedf68a46e41 [diff]
Build file lists for general-tests and device-tests

Add build targets that will just spit out a list of what files will be
in general-tests.zip and device-tests.zip, so that these can be
referenced by other tools without needing to actually build any
artifacts.

Test: m device-tests-files-list, m general-tests-files-list
Bug: 378926009
Change-Id: Ifc30a38ef97cf7a199f146bb6cf63d13d2f44f1d
2 files changed
tree: b056e94a7943a9187553bc56e27f0f841d16efa4
  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.