| commit | dec6e8e056871b1b840293a417ee28cb395d49fa | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Fri Jan 03 13:26:36 2020 -0800 |
| committer | Dan Willemsen <dwillemsen@google.com> | Fri Jan 03 19:19:11 2020 -0800 |
| tree | b04c1e5ff89b05c231281d11d90ff0530058a4d6 | |
| parent | 6e54952b44c230fc17cf42aab1a218c08238ea3b [diff] |
Export list of "installable" files to soong_ui These are a (partial) list of files that we'd install with a default build. The idea is that if something is removed from this list, soong_ui can remove it from the installed location before running ninja. It's okay if there are things missing from this list, it's not intended to be a 100% solution replacing installclean / CleanSpec.mk, just something that handles 80% of the cases without user involvement. In particular, if something is removed from PRODUCT_PACKAGES, we'll remove it from disk, but not necessarily rebuild the image files. That's the same as most use cases of CleanSpec.mk today, and often some other change will trigger the necessary images to be rebuilt. We should be able to fix that by changing all of the image creation rules to depend on the (partial) list of files they care about, or by fixing ninja to rebuild things when their list of dependencies change. (Other tools run into this same problem) The list of test files is also included so that we can remove obsolete tests from their "installed" locations within test suites and the testcases folders. Test: remove a module from PRODUCT_PACKAGES, see the print and file removed Test: change the name of a cts test, see the old one removed from cts Change-Id: I67f270a6713369099ca523aaf991ee3beb815c0a
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.