summaryrefslogtreecommitdiffstats
path: root/build/apk_test.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Remove the dependency on the STRIP env variable for Androidpeter@chromium.org2012-08-161-0/+1
| | | | | | | | | | | | Android builds currently rely on the STRIP environment variable to be available during build time, rather than just at project generation time. It shouldn't. BUG=142642 Review URL: https://chromiumcodereview.appspot.com/10832295 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151886 0039d316-1c4b-4281-b951-d872f2087c98
* Remove uses of Android's test runner's --ant-compile, as well as the flag ↵peter@chromium.org2012-08-151-1/+0
| | | | | | | | | | | | | | itself. It has been superseded by --sdk-build, which has already been set for all other Chromium and WebKit users. BUG= Review URL: https://chromiumcodereview.appspot.com/10855147 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151709 0039d316-1c4b-4281-b951-d872f2087c98
* Android's native_tests.gyp should take WebKit's directory structure into ↵peter@chromium.org2012-08-131-0/+2
| | | | | | | | | | | | account. This broke the WebKit Chromium Android bot. BUG=142322 Review URL: https://chromiumcodereview.appspot.com/10829291 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151257 0039d316-1c4b-4281-b951-d872f2087c98
* Make java.gypi export jar path to input_jars_paths variablecjhopman@chromium.org2012-08-091-2/+5
| | | | | | | | | | | | | | | | | Both java.gypi and apk_test.gypi expect the jar path in input_jars_paths. This means that we were specifying the dependence in both 'dependencies' and 'input_jars_paths'. This change makes it so that we don't need that redundancy. Also, make java.gypi use input_jars_paths in its input so that we actually rebuild targets when we should. BUG=136756 Review URL: https://chromiumcodereview.appspot.com/10837143 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150850 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Add chrome_java target for building Java code in the chromium layer.yfriedman@chromium.org2012-08-061-1/+12
| | | | | | | | | | | Also includes a refactoring of the Ant xml scripts to use a common template (contributed by shashishekhar@chromium.org). As part of this, I also continued Torne's effort of removing our reliance on environment variables. Unfortunately this currently means that you have to specify 5 gyp flags: ANDROID_SDK, ANDROID_SDK_ROOT, ANDROID_SDK_TOOLS, ANDROID_SDK_VERSION, ANDROID_TOOLCHAIN. This'll get better as we make further use of the checked in sdk both upstream and downstream. The problem stems from the android tree and released sdk having different configurations. Review URL: https://chromiumcodereview.appspot.com/10830012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150172 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce the --sdk-build flag for Android's native test generatorpeter@chromium.org2012-08-011-1/+1
| | | | | | | | | | | | | This flag supersedes --ant-compile and takes its value from gyp's sdk_build variable. It will tell the native test generator script to use Ant for Java compilation (default) instead of the Android.mk file. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10821128 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149440 0039d316-1c4b-4281-b951-d872f2087c98
* Add the target ABI option for apk based test runneryongsheng.zhu@intel.com2012-05-301-0/+2
| | | | | | | | | | | | | | Remove the hardcode directory name 'armeabi' and replace it with the Android target ABI information. Trivial gyp changes that are android-specific; TBRing some owners TBR=mark@chromium.org,jam@chromium.org,sky@chromium.org BUG=128944 TEST= Review URL: https://chromiumcodereview.appspot.com/10383263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139512 0039d316-1c4b-4281-b951-d872f2087c98
* Fix ninja build for android.yfriedman@chromium.org2012-05-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The primary issues is specifying the right path to PRODUCT_DIR (i.e. out/Release). The gyp generator for make specifies the absolute path but for ninja would use a relative path. Since the gyp targets don't line up with where the ant build files are located this causes failures such as base's java being generated in base/android/out/Release/... See: https://groups.google.com/forum/#!msg/gyp-developer/K2T_9obUya0/qq78_Ut-E-AJ for details. A couple of other minor fixes: - content java files are placed in out/Release/java/content to be consisent with other packages. - shared-libraries are now referenced by correct variables for apk-based tests - removed unused media/base/android/java/java.gyp (target is in media/media.gyp) TBR=mark@chromium.org,ben@chromium.org,rsleevi@chromium.org Review URL: https://chromiumcodereview.appspot.com/10386188 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139418 0039d316-1c4b-4281-b951-d872f2087c98
* Add APK targets for content_unittests and net_unittests.nileshagrawal@chromium.org2012-05-251-0/+55
- Add a gyp template to simplify adding new targets. - Add support for multiple jars in the test APK. BUG=125059 TEST= Review URL: https://chromiumcodereview.appspot.com/10399126 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139106 0039d316-1c4b-4281-b951-d872f2087c98