| commit | c0bd8c7611db5afc57f81ef4776eecb55e38d4af | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Jun 29 10:46:22 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Wed Jul 01 13:08:40 2020 +0900 |
| tree | 5b0d0699a75c1d805e85f7f873d6017019379091 | |
| parent | dd3af422a244d49b7c537cde9afdb765bbba0d59 [diff] |
Move build.prop to ./etc subdir for some partitions build.prop files under system_ext, product, and odm partitions are moved to the ./etc subdirectory. This is to be in-line with the established practice of having all configuration files under ./etc subdir. build.prop doesn't need to be an exception. However, system/build.prop and vendor/build.prop were not moved because there are a lot of apps and tools that depend on the path. Bug: 158735147 Test: device has build.prop under ./etc and is bootable Change-Id: I37c79f7337680f92406d9e196e5762bb8e7da5d8
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.