| commit | 618f1b2c0c902b3e1af4d3e0ac51a91a40b983e4 | [log] [tgz] |
|---|---|---|
| author | Patrik Fimml <patrikf@google.com> | Wed Nov 21 15:39:13 2018 +0100 |
| committer | Patrik Fimml <patrikf@google.com> | Fri Dec 21 11:53:09 2018 +0000 |
| tree | 50e7ab99cde5b2cc4b71019023b007942a646651 | |
| parent | 03ad10369548cbf8031d4561c1fee1bea95a039e [diff] |
Push cameraserver downstream from base_system.mk. Some non-phone form factors don't want cameraserver to save storage and RAM. Pushing it down to handheld and other build files allows selective inclusion to happen there. Intended to be a no-op refactoring, will disable for ATV in a follow-up CL. Bug: 118369095 Test: built system image for random device as smoke test Change-Id: I260fa5c9e512341d6a6824afebd5e8273fa5e66c Merged-In: I260fa5c9e512341d6a6824afebd5e8273fa5e66c
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.