| commit | 8e4024c87274969291f5ab7f517ce48b158afb61 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Mon Aug 14 15:25:32 2023 -0700 |
| committer | Cole Faust <colefaust@google.com> | Mon Aug 14 15:28:05 2023 -0700 |
| tree | 10dd5c6c7d45bfe6af047b4fc8ecc11a2309fd31 | |
| parent | 23a778b3613dc762e31145ed75728095a5b2b89d [diff] |
Rename some variables in definitions.mk Sublime text has an issue with their syntax highlighting, where it looks for \s*define\b to indicate the start of a define block. We had some variables that started with "define-", which match this regex, which causes Sublime to be confused about where the defines start and end. Rename the variables to work around this issue. Test: m nothing Change-Id: I997929606e2b0a8b086ad3b67a7ce1b5e99a7385
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.