Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / c21dc3c8c165bfd15f3c10eb9ce89666aaedd56f
commitc21dc3c8c165bfd15f3c10eb9ce89666aaedd56f[log] [tgz]
authorYuntao Xu <yuntaoxu@google.com>Thu Mar 17 18:39:36 2022 -0700
committerYuntao Xu <yuntaoxu@google.com>Thu Apr 07 11:01:19 2022 -0700
treeb737b5d3a94e48d29b705336124a588f2c6be2ff
parentd3a9957616e03581f36581991f8fcb98d5a4c662 [diff]
Make file list by partitions for all lunch targets

1. Filtered out the Android.mk file if the Make modules on them are
   not in the PRODUCT_PACKAGES or the correspoding deps;
2. Merged the Android.mk file list by partitions for all lunch targets.

Bug: 225256154
Test: lunch aosp_coral-eng; m
out/target/product/coral/mk2bp_remaining.html
Test: python3 build/make/tools/mk2bp_partition.py

Change-Id: I40919e81ab3c6bd516379f0acd72932e8db50088
3 files changed
tree: b737b5d3a94e48d29b705336124a588f2c6be2ff
  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. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. tapasHelp.sh
  22. 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.