Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 3e5fcd8a612fad36b4d034a82ef3d1aaedcc71e6
commit3e5fcd8a612fad36b4d034a82ef3d1aaedcc71e6[log] [tgz]
authorSam Delmerico <delmerico@google.com>Wed Sep 21 10:56:49 2022 -0400
committerSam Delmerico <delmerico@google.com>Wed Sep 21 10:56:49 2022 -0400
tree199d95738eeb7af33a931f1ba72918240c4f9b59
parentb2bf9efa3290ea190788080c23e0168a9eb52e6e [diff]
temporarily disable roboleaf_tests.sh

When I enabled the envsetup_tests target on CI, this script was failing.
Rather than break the build again by enabling CI on a potentially
failing script, let's just disable this for now, enable the CI target,
and then this script can be enabled and tested in presubmits before
submitting.

Bug: 244771601
Test: build/make/tests/roboleaf_tests.sh
Change-Id: I7c3469b49258e37c0ff9b49dd8805031216a7570
1 file changed
tree: 199d95738eeb7af33a931f1ba72918240c4f9b59
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize_branch_for_release.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. 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.