| commit | 1e6573f85e25c49762bd80f7e43091eec2289bb1 | [log] [tgz] |
|---|---|---|
| author | Chong Zhang <chz@google.com> | Wed May 15 16:56:08 2019 -0700 |
| committer | Chong Zhang <chz@google.com> | Thu May 16 12:24:53 2019 -0700 |
| tree | d2cf3ef6f448dc7529436dd88d61173ff0468e4f | |
| parent | 43b86c0182ceac129c0d2665cc9a74f4f1a64764 [diff] |
Remove a few libs used by soft omx from vndk Soft omx plugins are already removed from vndk, these should have been removed together. Keeping them in vndk with have both 32 and 64 bit on system, but soft omx only uses one set. bug: 132466615 test: build and check these libs are now on vendor/lib. Change-Id: I0242ece971ac75266cdf84e2341e5fa4b087451b
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.