| commit | fc478d29266a19ec66335fad38f38a15b6836555 | [log] [tgz] |
|---|---|---|
| author | Peter Collingbourne <pcc@google.com> | Fri Aug 04 14:57:31 2023 -0700 |
| committer | Peter Collingbourne <pcc@google.com> | Fri Aug 04 15:05:24 2023 -0700 |
| tree | fd4071b28a27cd017113d76257032d8b9ad0f55b | |
| parent | 9997fdbacf90ba6a41a14e1bbc5b499dce7fd669 [diff] |
Remove architecture name from names of HOST_*.mk files. These makefiles are actually architecture-independent (as far as I can tell, the Darwin one doesn't have anything arch-specific and there's just one of them anyway), so let's remove the architecture name from the names of these files to make it easier to support new host architectures. Bug: 294584591 Change-Id: Ic4cb0bf393c53ac9593afb7c2c6a6e07fbe6079e
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.