summaryrefslogtreecommitdiffstats
path: root/build/android/create_standalone_apk_action.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Fix check_perms for r208246wjia@chromium.org2013-06-241-0/+41
| | | | | | | | | | | | | | | | | | | | | | | Reland https://codereview.chromium.org/17569006/ with check_perms fix. Support using loadable module for libpeerconnection on Android. Borrowed create_standalone_apk_action.gypi, create_standalone_apk.py and finalize_apk_action.gypi from https://codereview.chromium.org/14843017/ with some minor fix in create_standalone_apk_action.gypi. For some cases where libpeerconnection needs to be a loadable module, we need to add libpeerconnection.so into Chrome_apk. This patch takes 2 steps: 1. build chrome with libpeer_target_type=loadable_module. 2. add libpeerconnection.so into the apk file. TEST=run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" build/gyp_chromium build chrome re-run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" CHROMIUM_GYP_FILE="build/android/chrome_with_libs.gyp" build/gyp_chromium build chrome_with_libs install Chrome-with-libs.apk and it works for https://apprtc.appspot.com Review URL: https://codereview.chromium.org/17647002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208304 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 208246 "Support using loadable module for libpeerconnecti..."abodenha@chromium.org2013-06-241-41/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Caused check_perms failure on Linux ChromiumOS. See http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Full/builds/21371 > Support using loadable module for libpeerconnection on Android. > > Borrowed create_standalone_apk_action.gypi, create_standalone_apk.py and finalize_apk_action.gypi from https://codereview.chromium.org/14843017/ with some minor fix in create_standalone_apk_action.gypi. > > For some cases where libpeerconnection needs to be a loadable module, we need to add libpeerconnection.so into Chrome_apk. > This patch takes 2 steps: > 1. build chrome with libpeer_target_type=loadable_module. > 2. add libpeerconnection.so into the apk file. > > TEST=run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" build/gyp_chromium > build chrome > re-run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" CHROMIUM_GYP_FILE="build/android/chrome_with_libs.gyp" build/gyp_chromium > build chrome_with_libs > install Chrome-with-libs.apk and it works for https://apprtc.appspot.com > > R=cjhopman@chromium.org, mallinath@chromium.org, tommi@chromium.org > > Review URL: https://codereview.chromium.org/17569006 TBR=wjia@chromium.org Review URL: https://codereview.chromium.org/17573017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208285 0039d316-1c4b-4281-b951-d872f2087c98
* Support using loadable module for libpeerconnection on Android.wjia@chromium.org2013-06-241-0/+41
| | | | | | | | | | | | | | | | | | | | | Borrowed create_standalone_apk_action.gypi, create_standalone_apk.py and finalize_apk_action.gypi from https://codereview.chromium.org/14843017/ with some minor fix in create_standalone_apk_action.gypi. For some cases where libpeerconnection needs to be a loadable module, we need to add libpeerconnection.so into Chrome_apk. This patch takes 2 steps: 1. build chrome with libpeer_target_type=loadable_module. 2. add libpeerconnection.so into the apk file. TEST=run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" build/gyp_chromium build chrome re-run gyp: GYP_DEFINES="$GYP_DEFINES libpeer_target_type=loadable_module" CHROMIUM_GYP_FILE="build/android/chrome_with_libs.gyp" build/gyp_chromium build chrome_with_libs install Chrome-with-libs.apk and it works for https://apprtc.appspot.com R=cjhopman@chromium.org, mallinath@chromium.org, tommi@chromium.org Review URL: https://codereview.chromium.org/17569006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208246 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "[Android] Support building standalone APK in component build"dfalcantara@chromium.org2013-06-201-41/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This breaks the Android component build. This reverts commit 125e64a9eb6406446fb864aea9fa887521f19616. >> [Android] Support building standalone APK in component build >> >> Many people's workflows assume that they can install the APK created in >> out/Debug/apks. With the component build that APK is actually an >> "incomplete" APK that cannot be manually installed (or rather causes >> obscure errors when manually installed). >> >> This change does two things. First, it moves the "incomplete" APK >> output to out/Debug/<package_name>/<ApkName>.apk. This should prevent >> accidental installs of the "incomplete" APK. Second, it introduces an >> option (create_standalone_apk) that when doing a component build, if >> set, will merge the shared libraries into the "incomplete" APK to >> create a standalone APK. This standalone APK will be created in >> out/Debug/apks/. >> >> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=207345 >> >> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=207516 BUG= R=cjhopman@chromium.org Review URL: https://codereview.chromium.org/17291013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207587 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Support building standalone APK in component buildcjhopman@chromium.org2013-06-201-0/+41
| | | | | | | | | | | | | | | | | | | | | Many people's workflows assume that they can install the APK created in out/Debug/apks. With the component build that APK is actually an "incomplete" APK that cannot be manually installed (or rather causes obscure errors when manually installed). This change does two things. First, it moves the "incomplete" APK output to out/Debug/<package_name>/<ApkName>.apk. This should prevent accidental installs of the "incomplete" APK. Second, it introduces an option (create_standalone_apk) that when doing a component build, if set, will merge the shared libraries into the "incomplete" APK to create a standalone APK. This standalone APK will be created in out/Debug/apks/. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=207345 Review URL: https://chromiumcodereview.appspot.com/14843017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207516 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 207345 "[Android] Support building standalone APK in comp..."skyostil@google.com2013-06-201-41/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This broke building of ChromeTest.apk. See: http://chromegw.corp.google.com/i/clank.tot/builders/instrumentation-yakju-clankium-tot/builds/11555/steps/chrome_smoke_instrumentation_tests/logs/stdio > [Android] Support building standalone APK in component build > > Many people's workflows assume that they can install the APK created in > out/Debug/apks. With the component build that APK is actually an > "incomplete" APK that cannot be manually installed (or rather causes > obscure errors when manually installed). > > This change does two things. First, it moves the "incomplete" APK > output to out/Debug/<package_name>/<ApkName>.apk. This should prevent > accidental installs of the "incomplete" APK. Second, it introduces an > option (create_standalone_apk) that when doing a component build, if > set, will merge the shared libraries into the "incomplete" APK to > create a standalone APK. This standalone APK will be created in > out/Debug/apks/. > > Review URL: https://chromiumcodereview.appspot.com/14843017 TBR=cjhopman@chromium.org Review URL: https://codereview.chromium.org/17484010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207439 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Support building standalone APK in component buildcjhopman@chromium.org2013-06-201-0/+41
Many people's workflows assume that they can install the APK created in out/Debug/apks. With the component build that APK is actually an "incomplete" APK that cannot be manually installed (or rather causes obscure errors when manually installed). This change does two things. First, it moves the "incomplete" APK output to out/Debug/<package_name>/<ApkName>.apk. This should prevent accidental installs of the "incomplete" APK. Second, it introduces an option (create_standalone_apk) that when doing a component build, if set, will merge the shared libraries into the "incomplete" APK to create a standalone APK. This standalone APK will be created in out/Debug/apks/. Review URL: https://chromiumcodereview.appspot.com/14843017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207345 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2024-05-20 06:38:41 +0000