| commit | b9d09c68fd1a5ebd1c0a799315946fd111aceef4 | [log] [tgz] |
|---|---|---|
| author | Harshit Mahajan <harshitmahajan@google.com> | Tue Feb 20 17:58:02 2024 +0000 |
| committer | Harshit Mahajan <harshitmahajan@google.com> | Wed Feb 21 15:34:57 2024 +0000 |
| tree | a82c67abbbb5007fdf5c680cb0f23a3c9ed6677b | |
| parent | 753ac5e51681b09d88c85a89667b33e100022464 [diff] |
Add CrashRecovery build flag to move files Files need to be moved from platform to the new apex. Adding a flag to control this movement. More Details: go/conditionally-move-android-files Bug: b/289203818 Test: m Ignore-AOSP-First: merge conflicts in AOSP aosp/2942585 Change-Id: Id3674bd6a8a32f64d189b8ac17b222b9d7966f69 --- (cherry picked from https://android-review.googlesource.com/q/commit:b99913a726a99b85616270ebfccb4e74a0c71052 due to merge conflicts)
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.