| commit | 011255996c8509187ecbd828e31642f98b4f2035 | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Wed Mar 04 15:12:52 2020 -0800 |
| committer | Bill Peckham <bpeckham@google.com> | Thu Mar 05 11:20:33 2020 -0800 |
| tree | 463cccc0106c9bbc42155f9380343727c89578a3 | |
| parent | 503e4884ab72d56d35ed638c21f1f0bd42744736 [diff] |
Don't touch .installable_files for non-FULL_BUILD If we're not doing a full build, leave $(PRODUCT_OUT)/.installable_files* alone rather than truncating it. This prevents the clean logic in Soong from removing everthing that we're trying to use to build an image using the snod, vnod, etc. goals. Bug: 149460609 Test: make droid, make vnod, verify vendor.img Change-Id: I612e32621b8045d085829507f22f6385b859f0c2 Merged-In: I612e32621b8045d085829507f22f6385b859f0c2
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.