Trigger some java_apk.gypi actions for all builds
commit26b75098e8c908d024058c04737996fab919b3d7
authorcjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 11 Apr 2013 00:26:25 +0000 (11 00:26 +0000)
committercjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 11 Apr 2013 00:26:25 +0000 (11 00:26 +0000)
treeb58048bae7ffc74b6f3c4a77a3fb98da09bbe5d5
parent89912bea4551e1cd4570767862f722b21deac22b
Trigger some java_apk.gypi actions for all builds

This adds a fake output path to several actions in java_apk.gypi:
push_libraries
apk_install
strip_libraries (when component==shared_library)

Adding this fake output makes the build system think that these actions
always need to be run when building the corresponding APK (because the fake
output is never up-to-date).

For the first two actions, this is required to ensure that (when
gyp_managed_install==1) the APK on the device (and its libraries) are
always up-to-date. If a user switches the connected device, then these
actions must be run even if no files on the host changed.

For strip_libraries, we do not know at gyp-time what the real inputs to
the action are (i.e. all the library dependencies). Also, ninja does
some build magic such that if you change a library (base.so for example)
its dependencies will not necessarily change.

BUG=158821

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

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