We need a separate version of the All target for building WebView in the
Android tree which only depends on the native code we intend to build.
Create one (just containing libwebview for now) and make it the default
thing to build when CHROME_ANDROID_BUILD_WEBVIEW is set.
R=mnaganov@chromium.org
BUG=
Review URL: https://codereview.chromium.org/11096024
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160843 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
all_dependent_settings is more like the link_settings that we would like
to use here. This variable is used by java targets to set the classpath
for javac, i.e. to set the libraries that are needed by the target.
Use of direct_dependent_settings with export_dependent_settings causes
unnecessary duplication of all java dependencies for all of our java
library targets.
BUG=146049
TBR=sky,brettw
Review URL: https://chromiumcodereview.appspot.com/10986094
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160768 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
SDK to verify when an SDK path is set. The SDK path supersedes whatever
find_sdk is supposed to find.
Also: Reorganize the SDK and deployment target variables to be scoped more
appropriately. Add a mac_sdk_min variable to set the main argument to
find_sdk.
Review URL: https://chromiumcodereview.appspot.com/11068023
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160536 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The ant build files for each of the apks that we create consisted of
only fairly straightforward boilerplate. With the recent changes to
java_apk.gypi and the gyp targets we can now build these correctly from
a single .xml with the differences in how the targets are built being
reflected in the gyp files (and then passed into ant).
TBR=joth
BUG=145991
Review URL: https://chromiumcodereview.appspot.com/10959034
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160396 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The envsetup configuration for building WebView using the Android build
system has rotted. Rather than try to share the non_sdk_build_init code,
just repeat the (few) parts we need to avoid setting all the parts that
are inappropriate, and fix the parts that are wrong or outdated.
Also, upstream the common.gypi settings that are specific to the WebView
build.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11026038
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160188 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is a workaround for multiprocessing on Windows. Importing in Python on
Windows doesn't search for imports that don't end in .py (and aren't
directories with an __init__.py). So, add this wrapper to avoid having
people change their command line to add a .py when running gyp_chromium.
R=dmazzoni@chromium.org
Review URL: https://codereview.chromium.org/11066021
git-svn-id: http://src.chromium.org/svn/trunk/src/build@160151 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The Android device status checker will attempt to alert by email when
a device fails. If the email step generates an exception, we don't
want to fail the 'Device Status Check' build step, because that causes
the entire build to fail.
Review URL: https://chromiumcodereview.appspot.com/11013024
git-svn-id: http://src.chromium.org/svn/trunk/src/build@159936 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Currently chromium_testshell_test_apk and content_shell_test_apk compile
and package java files from two different directories. Supporting this
in a good way is a requirement for using a single ant template for all
apks.
Introduce a new gyp variable for apk/jar targets, generated_src_dirs.
Now, generated_src_dirs is for directories that contain .java files that
are generated at build time and additional_src_dirs is for extra normal
directories to include in the jar/apk.
Change content_shell_test_apk and chromium_testshell_test_apk to use
additional_src_dirs for their extra dirs.
Add documentation for the gyp variables for jar/apk targets.
Reorder the ant defines in the java.gypi and java_apk.gypi.
BUG=136756,146056
Review URL: https://chromiumcodereview.appspot.com/10987083
git-svn-id: http://src.chromium.org/svn/trunk/src/build@159299 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- This moves the gyp phase to bb_compile.
This should give a 45 second speedup to testers and will also
eliminate local goma failures from breaking testers (which
besides a gcc version check in gyp have no dependence on goma)
R=yaron
BUG=141805
Review URL: https://codereview.chromium.org/10979070
git-svn-id: http://src.chromium.org/svn/trunk/src/build@159212 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Since we will run instrumentation tests for multiple test APKs, this adds the
test APK name to the name of the buildbot step.
Without this change, we will have multiple buildbot steps with the same name
although they are running tests for different APKS. And as a result, the stdio
will end up pointing to the same content for each of these steps.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10979027
git-svn-id: http://src.chromium.org/svn/trunk/src/build@159099 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
cjhopman@chromium.org
lliabraa@chromium.org
torne@chromium.org
pkl@chromium.org
creis@chromium.org
ddorwin@chromium.org
aberent@chromium.org
ilevy@chromium.org
cmp@chromium.org
mark@chromium.org
shashishekhar@chromium.org
michaelbai@google.com
qtc746@motorola.com
glotov@chromium.org
dbeam@chromium.org
saintlou@chromium.org
scottmg@google.com
navabi@chromium.org
maruel@chromium.org
jknotten@chromium.org
msarda@chromium.org
eugenis@chromium.org
mkosiba@chromium.org
klundberg@chromium.org
pliard@chromium.org
newt@chromium.org
mihaip@chromium.org
peter@chromium.org
phajdan.jr@chromium.org