Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / build / 8dd846c45f83bc697676132a994e8f59bcec57af
commit8dd846c45f83bc697676132a994e8f59bcec57af[log] [tgz]
authorRyan Mitchell <rtmitchell@google.com>Mon Nov 26 14:32:40 2018 -0800
committerRyan Mitchell <rtmitchell@google.com>Tue Dec 04 20:53:29 2018 +0000
tree93656fcbf28a1ae8dacdfa205b08fda63bc35c4b
parentf21a8f5376f18faf3654fe88266de37496853775 [diff]
Add RRO partition specification in Makefiles

This adds support for overlays to be placed in the product and
product_services partitions.

   LOCAL_VENDOR_MODULE :=  true #/vendor/overlay
   LOCAL_ODM_MODULE := true #/vendor/odm/overlay
   LOCAL_PRODUCT_MODULE := true #/system/product/overlay
   LOCAL_PRODUCT_SERVICES_MODULE := true #
   /system/product_services/overlay

Bug: 110869880
Test: built overlay with different partitions and verified correct apk
location

Change-Id: I21f594e784a18cf59f4ff03c00e30b463ec85008
1 file changed
tree: 93656fcbf28a1ae8dacdfa205b08fda63bc35c4b
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.mk
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  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.