Google Git
Sign in
android / platform / build / a0171af06f
commita0171af06ffca1080bf5196f628808ef07ccb6ea[log] [tgz]
authorJerome Gaillard <jgaillard@google.com>Thu Oct 10 19:35:08 2019 +0100
committerJerome Gaillard <jgaillard@google.com>Tue Oct 15 17:27:43 2019 +0100
tree45051bfae3d7241df9009ee65df98ec2e7a5a756
parent75d8a470399d13bfd63d5f3fcdc13410d8238d8d [diff]
Allow files generated by droidstubs to be copied in the SDK

We need to get files generated by a droidstubs target into the SDK. So
we first copy them into the out/target/common/obj/PACKAGING folder where
they can be picked up by the SDK build.

Bug: 142480924
Test: m sdk
Change-Id: I7a0b22907603e1d17ac05901ee7f8bb9cff89f7f
3 files changed
tree: 45051bfae3d7241df9009ee65df98ec2e7a5a756
  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. README.md
  17. tapasHelp.sh
  18. 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.