| commit | 675b92638dcfa11ff6337591611524ea2fdd16cb | [log] [tgz] |
|---|---|---|
| author | Chen Xu <fionaxu@google.com> | Thu Aug 15 15:48:42 2019 -0700 |
| committer | Jordan Liu <jminjie@google.com> | Wed Sep 11 13:13:05 2019 -0700 |
| tree | f5a6312600da7d9df24d7e83022b472f4c265dd7 | |
| parent | 5242dc18bfd13164dcbb02280153d72af9508168 [diff] |
prepare cellbroadcastreceiver to be a mainline module 1. prepare two build targets one for updatable module another for the legacy platform module with diferent config 2. a new cellbroadcastpermissionconfig module to expose a signature permission. 3. by default, the build include the legacy version. Later we will switch to the updatable module after more validation e.g, usre data migration due to uid change 4. for go devies, always include the platform cellbroadcast to to avoid creating new process Bug: 135956699 Test: unit test and test app Change-Id: I4d757e27b1e36fbf4890d08afbd45a141bccfc7c Merged-In: I4d757e27b1e36fbf4890d08afbd45a141bccfc7c
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.