Forwarder used to be a pain to setup/tear down across all the various
harnesses.
This CL should hopefully solve these issues by hiding these
implementation details. The host daemon is now killed once the first time that
the Forwarder class is used and the daemon running on the devices is also
killed the first time a port is forwarded for a specific device.
TBR=bulach@chromium.org
BUG=242846
Review URL: https://codereview.chromium.org/19550004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212582 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Currently, this has only the following capabilities:
+ Authenticate using a Google account on the phone
+ Query and display the host list from the Chromoting directory server
+ Connect to and communicate with the host service over XMPP/ICE
+ Establish peer-to-peer channels for communicating with the host service
Notable missing features are:
- Display the host's desktop
- Handle any kind of input
Review URL: https://chromiumcodereview.appspot.com/19506004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212496 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Original CL here: https://codereview.chromium.org/17619005/
Changed since previous landing is diff between ps1 and ps2.
Diff since previous landing is a bit noisy, but in those files
against original is relatively small. The conditions for the
defines were incorrect and are simpler (and correct) now.
Previously:
Create top-level separate targets for browser and child dlls
The general idea is that there's top level targets chrome and chrome_child,
and corresponding content_app and content_app_child that depend on only
the subtargets that should be included in the appropriate dll.
Currently (probably) Windows-only and requires setting chrome_multiple_dll=1
for gyp.
Links, but Blink is still included in browser.
Single-process mode is currently disabled when chrome_multiple_dll is set.
Current graph is at:
http://commondatastorage.googleapis.com/chromelinkgraph/deps.html generated by
"python tools\win\split_link\graph_dependencies.py deps.html"
Remove the previous hacky-er attempt at this that was named "split dll".
TBR=jam@chromium.org
BUG=237249, 256965
Review URL: https://codereview.chromium.org/19572013
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212415 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is to move back icu headers in
third_party/icu/public/{i18n,common}/unicode back to their upstream
locations in third_party/icu/source/{i18n,common}/unicode.
http://codereview.chromium.org/18836004 has is a CL to move
ICU header files.
Roll ICU to the version with the above ICU CL (http://crrev.com/211851 ).
In addition to the global replacement of third_party/icu/public with third_party/icu/source, the top-level DEPS, DEPS in printing and chrome/ are tightened up. (the latter two were too permissive (it used to allow any header from third_party/icu).
Besides, sync '-foo' list in ios/public/DEPS with '+foo' in the top-level DEPS and build/linux/unbundled/icu.gyp is updated.
BUG=251433
TEST=Compile succeeds on all bots. checkdeps.py does not find any error.
TBR=brettw,sky,wtc
Review URL: https://chromiumcodereview.appspot.com/18252003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212324 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Caused Linux x64 sizes to fail for reasons unclear.
> Create top-level separate targets for browser and child dlls
>
> The general idea is that there's top level targets chrome and chrome_child,
> and corresponding content_app and content_app_child that depend on only
> the subtargets that should be included in the appropriate dll.
>
> Pull bluetooth_utils from bluetooth_device into separate common target
> as it's referenced from chrome/common/extensions.
>
> Currently (probably) Windows-only and requires setting chrome_multiple_dll=1
> for gyp.
>
> Links, but Blink is still included in browser.
>
> Single-process mode is currently disabled when chrome_multiple_dll is set.
>
> Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html
> generated by "python tools\win\split_link\graph_dependencies.py deps.html"
>
> Remove the previous hacky-er attempt at this that was named "split dll".
>
> TBR=jam@chromium.org
>
> BUG=237249,256965
>
> Review URL: https://codereview.chromium.org/17619005TBR=scottmg@chromium.org
Review URL: https://codereview.chromium.org/19572012
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212239 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The general idea is that there's top level targets chrome and chrome_child,
and corresponding content_app and content_app_child that depend on only
the subtargets that should be included in the appropriate dll.
Pull bluetooth_utils from bluetooth_device into separate common target
as it's referenced from chrome/common/extensions.
Currently (probably) Windows-only and requires setting chrome_multiple_dll=1
for gyp.
Links, but Blink is still included in browser.
Single-process mode is currently disabled when chrome_multiple_dll is set.
Current graph is at: http://commondatastorage.googleapis.com/chromelinkgraph/deps.html
generated by "python tools\win\split_link\graph_dependencies.py deps.html"
Remove the previous hacky-er attempt at this that was named "split dll".
TBR=jam@chromium.org
BUG=237249,256965
Review URL: https://codereview.chromium.org/17619005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212230 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This causes flakiness on the Android debug tester bot.
> Move Python setup/tear down logic into Forwarder itself.
>
> Forwarder used to be a pain to setup/tear down across all the various
> harnesses.
> This CL should hopefully solve these issues by hiding these implementation
> details. The host daemon is now killed once the first time that the Forwarder
> class is used and the daemon running on the devices is also killed the first
> time a port is forwarded for a specific device.
>
> BUG=242846
> R=bulach@chromium.org, frankf@chromium.org
>
> Review URL: https://codereview.chromium.org/18086004TBR=pliard@chromium.org
Review URL: https://codereview.chromium.org/19576005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212054 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Adds an option to print the device status information (i.e. online devices, offline devices and device battery levels). Example output:
<*>RESULT OnlineDevices: OnlineDevices= 2
RESULT OfflineDevices: OfflineDevice= 0
RESULT DeviceBattery: 0149CC380F016011= 99
RESULT DeviceBattery: 014E378305007013= 60
Cleanup uses AndroidCommands for calling adb shell commands rather than its own GetCmdOutput function.
BUG=254014
Review URL: https://chromiumcodereview.appspot.com/19284009
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212052 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Forwarder used to be a pain to setup/tear down across all the various
harnesses.
This CL should hopefully solve these issues by hiding these implementation
details. The host daemon is now killed once the first time that the Forwarder
class is used and the daemon running on the devices is also killed the first
time a port is forwarded for a specific device.
BUG=242846
R=bulach@chromium.org, frankf@chromium.org
Review URL: https://codereview.chromium.org/18086004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@212020 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
I'm guesing we haven't built this since rolling the NDK. I see errors of
the form:
In file included from ../../third_party/webrtc/modules/audio_coding/codecs/isac/fix/source/entropy_coding_neon.c:19:0:
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h: In function 'vshr_n_s32':
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h:3426:3: error: argument must be a constant
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h: In function 'vshl_n_s32':
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h:3798:3: error: argument must be a constant
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h: In function 'vshll_n_s16':
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h:4032:3: error: argument must be a constant
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h: In function 'vset_lane_s32':
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h:5082:3: error: argument must be a constant
third_party/android_tools/ndk/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.6/include/arm_neon.h:5082: confused by earlier errors, bailing out
One additional fix to md5sum is included.
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/18034029
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211835 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The perf bots run with -v (INFO level debugging). I'm moving the noisiest
output to DEBUG level. This will make the android log output more parsable
so that the real failures are easier to spot.
Also, this cuts down on several commands running between each page.
BUG=None
TEST=smoothness and page_cycler on android
Review URL: https://chromiumcodereview.appspot.com/18764005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211673 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
check_perms failues on Linux bots.
http://build.chromium.org/p/chromium/builders/Linux/builds/40809/steps/check_perms/logs/stdio
> /b/build/slave/Linux/build/src/build/sanitize-mac-build-log.sed: Has executable bit but not shebang
> /b/build/slave/Linux/build/src/build/sanitize-win-build-log.sed: Has executable bit but not shebang
> Cleanup sanitize build sed and sh scripts.
>
> Minor cleanup:
> * switch regexes to extended regexes,
> which remove a few gratuitous backslashes
> (and makes them less confusing, since basic regexes are so rarely used)
> * fix . -> \. (which *does* need escaping in either case)
> * make sed files non-executable,
> since if executed they just say "don't execute this"
> * delete blank line
>
> (Just noticed these scripts when working on Blink IDL bindings, and made
> necessary fixes for my changes, but cleaning up while I'm here.)
>
> Review URL: https://chromiumcodereview.appspot.com/19052002TBR=nbarth@chromium.org
Review URL: https://codereview.chromium.org/19129002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211566 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Minor cleanup:
* switch regexes to extended regexes,
which remove a few gratuitous backslashes
(and makes them less confusing, since basic regexes are so rarely used)
* fix . -> \. (which *does* need escaping in either case)
* make sed files non-executable,
since if executed they just say "don't execute this"
* delete blank line
(Just noticed these scripts when working on Blink IDL bindings, and made
necessary fixes for my changes, but cleaning up while I'm here.)
Review URL: https://chromiumcodereview.appspot.com/19052002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@211564 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
tfarina@chromium.org
pvalenzuela@chromium.org
gkanwar@google.com
cbiesinger@chromium.org
pliard@chromium.org
ilevy@chromium.org
frankf@chromium.org
solb@chromium.org
mnaganov@chromium.org
craigdh@chromium.org
justincohen@google.com
scherkus@chromium.org
scottmg@chromium.org
jshin@chromium.org
yfriedman@chromium.org
gkanwar@chromium.org
andrewhayden@chromium.org
sivachandra@chromium.org
navabi@google.com
apatrick@chromium.org
thakis@chromium.org
raphael.kubo.da.costa@intel.com
jochen@chromium.org
jam@chromium.org
fischman@chromium.org
enne@chromium.org
tonyg@chromium.org
mark@chromium.org
yukishiino@chromium.org
peter@chromium.org
rmcilroy@chromium.org
tkent@chromium.org
nbarth@chromium.org