| commit | cd0e477d8fca9e8cd4bae2a0e296a048945614c1 | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Mon Apr 15 20:32:14 2019 +0900 |
| committer | Inseob Kim <inseob@google.com> | Tue Apr 23 10:11:14 2019 +0900 |
| tree | 7f75ac47b13ff7d2602d8aa511c1aa5b09f57f51 | |
| parent | 22c434e80f89d348d6c99be3c6836f8ed26e2ce3 [diff] |
Build contexts files with Soong This is to migrate sepolicy Makefiles into Soong. For the first part, file_contexts, hwservice_contexts, property_contexts, and service_contexts are migrated. Build-time tests for contexts files are still in Makefile; they will also be done with Soong after porting the module sepolicy. The motivation of migrating is based on generating property_contexts dynamically: if we were to amend contexts files at build time in the future, it would be nicer to manage them in Soong. To do that, building contexts files with Soong can be very helpful. Bug: 127949646 Bug: 129377144 Test: 1) Build blueline-userdebug, flash, and boot. Test: 2) Build blueline-userdebug with TARGET_FLATTEN_APEX=true, flash, and boot. Test: 3) Build aosp_arm-userdebug. Change-Id: I486f7065207468697320776f726b732077656c6c
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.