Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 11767d5dca4d035a10f784494a332d24e5104b0a
commit11767d5dca4d035a10f784494a332d24e5104b0a[log] [tgz]
authorLuca Farsi <lucafarsi@google.com>Thu Mar 07 13:33:57 2024 -0800
committerLuca Farsi <lucafarsi@google.com>Mon Mar 18 14:19:01 2024 -0700
tree9cc6806cf3c4df481f7b28dfc92fe8fcd99457ac
parentafac5b33ac8f6e170a820577f1cadf443df75d7d [diff]
Change the build test suites script to be noop

In preparation of switching over the git_main test suites target to
using this script change it to a no-op first to insure there's no
initial impact.

Test: ./build/make/ci/build_test_suites-trunk_staging --target_product aosp_x86_64 --target_release trunk_staging --with_dexpreopt_boot_img_and_system_server_only
Bug: 314171817
Change-Id: I7afab933143e4b617866b1975b1cbc71107f5b2f
2 files changed
tree: 9cc6806cf3c4df481f7b28dfc92fe8fcd99457ac
  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.