Google Git
Sign in
android / platform / build / c0423c8dae0e571e90d06cdced6c70a67d91cbf5
commitc0423c8dae0e571e90d06cdced6c70a67d91cbf5[log] [tgz]
authorAnton Hansson <[email protected]>Wed Jan 13 09:32:48 2021 +0000
committerAnton Hansson <[email protected]>Wed Jan 13 11:04:02 2021 +0000
tree04339caa78e6a25ba4cad5b3bb6de71d7d121b72
parent04a80cd736b69c8419ca43fb939ff54773dc78c2 [diff]
Use 64 bit binder in module builds

Add a new BoardConfigModuleCommon for settings of this sort.

Bug: 176840868
Test: forrest module coverage build
Change-Id: Ie62261ecc0f0967f677a890a382fa1da060f7ff2
5 files changed
tree: 04339caa78e6a25ba4cad5b3bb6de71d7d121b72
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. rbesetup.sh
  17. README.md
  18. tapasHelp.sh
  19. 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.