| commit | 45cf3489406836fdf079ddd09c071abd72d2260f | [log] [tgz] |
|---|---|---|
| author | sandeepbandaru <sandeepbandaru@google.com> | Mon Nov 11 11:03:38 2024 +0000 |
| committer | Sandeep Bandaru <sandeepbandaru@google.com> | Wed Dec 04 21:48:25 2024 +0000 |
| tree | aadabe3e846064df60eb96c14424263cf88724b4 | |
| parent | 9f20312c5b4f7fe44a4dcf45cddee3834db65294 [diff] |
Add build make config for allowing framework and service jars We use the build-flag to allow switching the jars between apex and platform. Flag: build.release_ondevice_intelligence_module Bug: 376427781 Change-Id: I8f4b0c199ecbac7106b45bec966b0f2b4e53aef7 Ignore-AOSP-First: related changes in internal-topic
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.