| commit | 003635c95ecb9d800a8928db0793a994969f7f27 | [log] [tgz] |
|---|---|---|
| author | Aaron Kling <webgeek1234@gmail.com> | Thu Oct 03 02:59:07 2024 -0500 |
| committer | Luca Stefani <luca.stefani.ge1@gmail.com> | Sun Oct 20 18:27:44 2024 +0200 |
| tree | 103d693e04cfb3f5080b25fa00421d40baf4c529 | |
| parent | c6d0aca4bd057049465970f6fbf0eddd9a2df5fd [diff] |
core/Makefile: Fix filenames with commas Prior to this, any filenames with commas, for example device specific nvrams or hcds compatible with the mainline kernel, would cause a build failure because GNU make can't handle passing an argument with a comma because comma is the delimiter. To work around this pass the arguments via variables local to the rule. Change-Id: I852b36d7194394389a63683fc8c68474f8323d9b
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.