commit | 9dd9e680b9711e9bfd9c9503bb9df4c8b4e29a97 | [log] [tgz] |
---|---|---|
author | Shibin George <shibing@codeaurora.org> | Mon Jul 02 16:21:49 2018 +0530 |
committer | Shibin George <shibing@codeaurora.org> | Wed Jul 04 18:05:07 2018 +0000 |
tree | 58ad2e0897720766e490074965f2939789c8d73e | |
parent | 8c01b71e2d32f642bdf225dc5725d3e22da9a8b8 [diff] |
Allow multiple profiles to be added as part of boot.prof Extend PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION such that multiple text-based profiles can be fed to profman to be included in boot.prof BUG: 70292748 Test: profman with --dump-only option shows that additional text-based profiles are also being read if they have been added to PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION Change-Id: I8a6437a323e43b61612c67038abdde200607c513
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.