| commit | 4f60e366dbc279418f52b2146736b74adf45c577 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed Jun 05 11:53:43 2019 -0700 |
| committer | Colin Cross <ccross@android.com> | Thu Jun 06 12:51:47 2019 -0700 |
| tree | 83c4ababbab81c1c1968327a8e8ae04a3f11d609 | |
| parent | 9c560f17a8b9b51f96bb24d8e0b108c68ec1247e [diff] |
Make kernel modules into normal installed files We sometimes see build failures when building platform.zip happens at the same time as building vendor.img if the vendor.img rule runs rm -rf $OUT/vendor/lib/modules at the same time that platform.zip is zipping $OUT/vendor/. Move the kernel modules into normal installation rules so that they are in place by the time either the vendor.img or platform.zip rules run. This will also cause the kernel modules to show up in installed-files*.txt. Test: m vendorimage && ls $OUT/vendor/lib/modules Change-Id: I178b1d54bfcdb5cf5c29885ace9183ac28fc8826
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.