Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 88feffcb1a6f5aff70fcd1575a14a323fd485033
commit88feffcb1a6f5aff70fcd1575a14a323fd485033[log] [tgz]
authorLuca Farsi <lucafarsi@google.com>Tue Feb 13 12:09:08 2024 -0800
committerLuca Farsi <lucafarsi@google.com>Tue Feb 20 17:33:32 2024 -0800
treeb7a15c278051694f5fde324c44534d101f018fbe
parent9b3d6f91aa73ee8cdf4121a90bc36e9aee6213ca [diff]
Build config file zips

Build general-tests_configs.zip and general-testlist.zip as part of the
build_test_suites step, which general-tests also outputs.

Test: BUILD_NUMBER="P0" ./build/make/ci/build_test_suites --target_product aosp_x86_64
--target_release trunk_staging --with_dexpreopt_boot_img_and_system_server_only --dist_dir <dist_dir> --change_info <change_info_file> <extra_targets>
Bug: 314171817

Change-Id: Ic324ed4e5a05e1308dee3af7f15c067f88018b2d
1 file changed
tree: b7a15c278051694f5fde324c44534d101f018fbe
  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.