Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 407d214b0da7870619a621d446691caa1edb9f32
commit407d214b0da7870619a621d446691caa1edb9f32[log] [tgz]
authorCole Faust <colefaust@google.com>Mon Oct 24 17:57:39 2022 -0700
committerCole Faust <colefaust@google.com>Mon Oct 24 17:57:39 2022 -0700
tree84e6b7407d3f90c93fc0ed28e8ae1b3b1f5155ab
parent3946ea03181421c9d4a2ad0ff494e415540c0ee6 [diff]
Convert findleaves.py to python 3

Kati special-cases findleaves.py to an internal
C++ implementation, so I don't think this python
script is even used. Update it anyways, and
test by manually running findleaves.py.

Bug: 203436762
Test: ./build/make/tools/findleaves.py --mindepth=2 --dir=build/make/target Android.mk
Change-Id: If27cc37d8f673388c0e31b9491e792b98ca59da4
1 file changed
tree: 84e6b7407d3f90c93fc0ed28e8ae1b3b1f5155ab
  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-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-step-1.sh
  17. finalize_branch_for_release.sh
  18. help.sh
  19. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  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.