Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / e1b4f302e5464c66e9198943ce66905843d73da3
commite1b4f302e5464c66e9198943ce66905843d73da3[log] [tgz]
authorColin Cross <ccross@android.com>Thu Jun 14 14:38:22 2018 -0700
committerColin Cross <ccross@android.com>Thu Jun 14 14:38:54 2018 -0700
tree08ede9ccc6bb339d05dc7c2d747fd3fafd59902e
parent6021800c459d1161897aad5c7997f79d760a25ba [diff]
Move merged AndroidManifest.xml file to manifest subdirectory

Some modules generate their own custom AndroidManifest.xml file
to $(intermediates.COMMON)/AndroidManifest.xml file.  Move the
build system's location to
$(intermediates.COMMON)/manifest/AndroidManifest.xml.

This location will also be used later for finding manifest files
from LOCAL_STATIC_ANDROID_LIBRARIES dependencies.

Bug: 78447299
Test: m checkbuild
Change-Id: I345f079bdd191451333b38d882418f2f7150b1e9
Merged-In: I345f079bdd191451333b38d882418f2f7150b1e9
(cherry picked from commit 00a6348e7dfa4fafc308ab92d8e7d06dcfcd01ba)
2 files changed
tree: 08ede9ccc6bb339d05dc7c2d747fd3fafd59902e
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. 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.