| commit | c244c21573689bb8fa4b389f909b9f77dd9f2f9a | [log] [tgz] |
|---|---|---|
| author | Ivan Lozano <ivanlozano@google.com> | Thu Jan 10 09:46:52 2019 -0800 |
| committer | Ivan Lozano <ivanlozano@google.com> | Tue Jan 15 13:05:59 2019 -0800 |
| tree | 60d46495dd449834d6e540e2bab5ba7fac9335d6 | |
| parent | db3c8985be5165d84ba7f15886827046340a1ecf [diff] |
Enable execute-only memory layouts by default. This enables execute-only memory (XOM) layouts to be used by default in the build system. As of now, there's only support for ARM64 devices, so this only affects those. Since userland XOM requires kernel support, devices without the necessary support will continue to allow pages marked execute-only to be read and they should be unaffected by this. Bug: 77958880 Test: Device with and without kernel support boot. Test: Binary throws segfault when reading from XOM on supported device. Test: Debugger works and stack traces are still generated correctly. Test: Teamfooding, stable during regular usage. Change-Id: I8db4235c8e60eea6d701bdf3c43b79a06d6b01cd
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.