Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 985526c5ac5d20194e8558dda014ee71aa57b794
commit985526c5ac5d20194e8558dda014ee71aa57b794[log] [tgz]
authornilac8991 <nilac8991@gmail.com>Sun Dec 17 13:08:18 2017 +0100
committerAren Clegg <compiterman2k3@live.com>Tue Sep 18 00:22:37 2018 +0000
tree189353c522553a9fd1556b7ef5afdbc3beb22f49
parentd68e2e8b4ad9d1c8bcccd9bc47178bfcd4bfa725 [diff]
build: Export TARGET_ARCH

Change-Id: I02ea0ea21dacf5c9bf1eb6b5c8b1590b84271a5b
Signed-off-by: nilac8991 <nilac8991@gmail.com>
2 files changed
tree: 189353c522553a9fd1556b7ef5afdbc3beb22f49
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. .gitreview
  7. Android.mk
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. envsetup.sh
  12. help.sh
  13. navbar.md
  14. OWNERS
  15. README.md
  16. tapasHelp.sh
  17. 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.