Push native libraries separately when gyp manages install

When an APK is installed, any native libraries it contains are
extracted to the APK's lib folder on the device. It is actually
possible to add, change, or remove libraries in that folder directly.

This means, that when gyp is managing the install of APKs, the APK does
not actually need to include the native library, and that can be pushed
separately.

This does several nice things:
libraries can be pushed while a .apk is building
.apk no longer needs to be rebuilt+reinstalled when a library changes
if native library isn't changed, it doesn't need to be zipped+installed
w/ component build, only changed libraries will need to be reinstalled

BUG=158821


Review URL: https://chromiumcodereview.appspot.com/13334003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@191888 0039d316-1c4b-4281-b951-d872f2087c98


CrOS-Libchrome-Original-Commit: 46aac2e9c09e577aea1190fa5356fbc4cef3be18
1 file changed
tree: c9cbd3627f3b4657870f29d8adfbdfb5ba2a12d7
  1. base/
  2. build/
  3. dbus/
  4. ipc/
  5. testing/
  6. third_party/