Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 2dc1701741f69189a1b5c92f50e17b98bf2f0ebe
commit2dc1701741f69189a1b5c92f50e17b98bf2f0ebe[log] [tgz]
authorLuca Farsi <lucafarsi@google.com>Tue Mar 19 16:47:54 2024 -0700
committerLuca Farsi <lucafarsi@google.com>Tue Mar 19 17:24:40 2024 -0700
tree3cefe1c39a5a805a243a3f52ab80661c8c1be230
parent6d5a509efa35199f1903caebe560fe3ca9f63f6f [diff]
Remove extra test targets from inside build script

Due to branch constraints, remove the extra targets defined inside the
build script and revert to having them be passed in via command line.

Test: ./build/make/ci/build_test_suites_x86_64-trunk_staging --target_product aosp_x86_64 --target_release trunk_staging --with_dexpreopt_boot_img_and_system_server_only <extra_targets>
Bug: 314171817
Change-Id: I89a82e969d294104f587d778ad319a41905320f8
2 files changed
tree: 3cefe1c39a5a805a243a3f52ab80661c8c1be230
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. banchanHelp.sh
  11. buildspec.mk.default
  12. Changes.md
  13. CleanSpec.mk
  14. cogsetup.sh
  15. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. METADATA
  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.