1) Rename WebViewMainDelegate to AwMainDelegate for consistency with
other classes.
2) Move gyp file to the top level and don't bother having separate gypi
files for the subcomponents for now; the file list is very short anyway
and is not going to be a significant source of contention between the
small number of webview developers at this time, and it's easier to see
what's going on if it's all in one place.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10893025
git-svn-id: http://src.chromium.org/svn/trunk/src/build@154020 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This creates a "libwebview" build target for the JNI code to power the
Android WebView. This is unfinished and can't run without additional
code that has not yet been upstreamed, but it compiles and links
successfully.
In its present state the WebViewMainDelegate reuses Chrome
implementations of other content client interfaces. This is a temporary
state of affairs until necessary refactorings can be performed.
Review URL: https://chromiumcodereview.appspot.com/10825155
git-svn-id: http://src.chromium.org/svn/trunk/src/build@150780 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This consists of a simple native program which dumps /proc/diskstats and
/proc/stat to a file at a regular interval. The dump is then processed host-side
into a JSON format which is charted in HTML via the Google Charts API.
The perf test runners are not upstreamed yet and when they are this will be part
of the set of profilers available.
BUG=136690
TEST=manual, run activity_monitor.py to try out.
Review URL: https://chromiumcodereview.appspot.com/10783020
git-svn-id: http://src.chromium.org/svn/trunk/src/build@147019 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
normal circumstances, so it makes more sense to treat it as if it were a
checked-in source file, not a generated file. The rule for its
generation was still getting run once on a clean build, because the
other targets that depended on it expected a gyp timestamp file to exist
for the target.
There's no need for any other targets to actually depend on lastchange
(and in fact several of the targets that make use of the file already
don't depend on the target); it should already exist, and if it doesn't
then the source checkout is probably broken (as the other steps in
runhooks are also mandatory). So, remove the rule entirely.
Review URL: https://chromiumcodereview.appspot.com/10388213
git-svn-id: http://src.chromium.org/svn/trunk/src/build@139765 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
OFF by default; enable with a gyp var. E.g.
GYP_DEFINES="$GYP_DEFINES gtest_target_type=shared_library" android_gyp
Some useful commands:
adb uninstall org.chromium.native_test
adb install -r out/Release/base_unittests_apk/ChromeNativeTests-debug.apk
adb shell am start -n org.chromium.native_test/org.chromium.native_test.ChromeNativeTestActivity
For the moment, all apks can be built simultaneously but use the same
activity name. Thus you cannot have more than one installed at the
same time.
BUG=None
TEST=
Review URL: http://codereview.chromium.org/10051021
git-svn-id: http://src.chromium.org/svn/trunk/src/build@133053 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
While we sort out the remaining linker errors, this at least ensures we
can add compliation of a bunch of chrome code for Android to gatekeeper.
This is motivated by having the android unit_tests compilation step
broken 4 out of 4 days this week.
BUG=117407
Review URL: http://codereview.chromium.org/10065018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@132154 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Promote DumpRenderTree and webkit_unit_tests to targets being part of All (thus
out of experimental), while also adding TestWebKitAPI by correctly referring to
WebKit's All.gyp instead of (the seemingly Windows-oriented) webkit/webkit.gyp.
After this change, three new targets will be build for Android on the main
waterfall. The compile time for new required files (they all rely heavily on
webkit.a) is negligible, link time is more significant, namely ~40 seconds per
target, but this will be parallelized on the bot with other targets. Increase
in build time is ~50 seconds on my T3500.
BUG=
TEST=DumpRenderTree, webkit_unit_tests and TestWebKitAPI should be build on the
Android buildbots.
Review URL: http://codereview.chromium.org/9701070
git-svn-id: http://src.chromium.org/svn/trunk/src/build@127459 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Move the dependency to the base target, causing Java to be compiled on all
configurations (including trybots and the main waterfall bot). We currently
build two source files.
BUG=
TEST=Build output should execute the "base_java" action.
Review URL: http://codereview.chromium.org/9699018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@126693 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Introduce the first java source for chrome on android to base/android/java.
Also add new target to build the java source in the directory. Currently
there is a dummy java file called DeleteStaging.java that should be replaced
when real base java source code is upstreamed. This will be the java files
from this patch: https://chromiumcodereview.appspot.com/9443018/. The
DeleteStaging.java file should be removed once real java code is checked in.
BUG=
TEST=
Review URL: http://codereview.chromium.org/9514018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@124134 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Fix install-build-deps-android.sh so it can be re-run cheaply.
Update install-build-deps-android.sh so it installs the 64-bit linker.
Run install-build-deps-android.sh each build on the FYI bot.
Move content_unittests to experimental so the FYI builder hits it.
BUG=None
TEST=
Review URL: http://codereview.chromium.org/9401029
git-svn-id: http://src.chromium.org/svn/trunk/src/build@122665 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
torne@chromium.org
mkosiba@chromium.org
ilevy@chromium.org
bulach@chromium.org
nileshagrawal@chromium.org
satish@chromium.org
wangxianzhu@chromium.org
rvargas@google.com
akalin@chromium.org
jrg@chromium.org
yfriedman@chromium.org
rsleevi@chromium.org
peter@chromium.org
navabi@google.com
creis@chromium.org
jrg@google.com
jingzhao@chromium.org
michaelbai@google.com