| commit | 2e92cfb701aab6dfff6f50234906e1ced0fe7e1c | [log] [tgz] |
|---|---|---|
| author | Tom Cherry <tomcherry@google.com> | Fri Nov 08 17:57:21 2019 -0800 |
| committer | Tom Cherry <tomcherry@google.com> | Fri Nov 08 17:58:31 2019 -0800 |
| tree | fe2274d2cec87e2714a5186ba3452efa52f6ade9 | |
| parent | 65e4ce6ebc871a963ddcdb3277e400b24602c4e6 [diff] |
Check property type in host_init_verifier We have all of the 'type' information for properties available during build time, so let's check this when setting properties in init. Test: setprop apexd.status bad results in: host_init_verifier: Command 'setprop apexd.status bad' (out/soong/.intermediates/system/core/rootdir/init.rc/android_x86_core/init.rc:927) failed: Property type check failed, value doesn't match expected type 'enum starting ready' host_init_verifier: Failed to parse init script 'out/soong/.intermediates/system/core/rootdir/init.rc/android_x86_core/init.rc' with 1 errors Test: CF builds without that error Change-Id: Ia1b24ab42e2193e3298021bc86ee2309ca7a381f
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.