commit | 22fb13e8d4bdf4338b0e264a20f329919bfc3912 | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Mon Apr 19 10:52:28 2021 +0100 |
committer | Anton Hansson <hansson@google.com> | Fri Apr 23 15:47:15 2021 +0100 |
tree | 46d749c574e448013b1dd9c4ce7b132e9ad056b9 | |
parent | af35677f030d2edae0ad640047abd40066b59932 [diff] |
Enable CFI for media module paths in module_* This is a step on the way to make module_arm64 to produce the same artifacts as aosp_arm64 when building unbundled modules. Bug: 185765252 Bug: 185789027 Test: compare media.swcodec apex build with module_arm64 and aosp_arm64 Merged-In: I50d29c1d57849fd915dc771bb8e9f028fbe8efcd Change-Id: I50d29c1d57849fd915dc771bb8e9f028fbe8efcd
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.