| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
BUG=
Review URL: https://codereview.chromium.org/1356173002
Cr-Commit-Position: refs/heads/master@{#350064}
|
| |
|
|
|
|
|
|
|
|
|
| |
1. Add dependency to the Cardboard SDK, which will be used to render 3D scenes.
2. Add new permissions: android.permission.NFC(required by the Cardboard SDK to access Cardboard's NFC tag), android.permission.READ_EXTERNAL_STORAGE and android.permission.WRITE_EXTERNAL_STORAGE(these permissions are required by the Cardboard SDK to pair the user's phone to their VR viewer).
3. Create VRDesktop activity enabling user to interact with the VR Chromoting desktop.
4. Create CardboardView renderer that will be used to generate 3D graphics.
Review URL: https://codereview.chromium.org/1231153002
Cr-Commit-Position: refs/heads/master@{#338730}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
manifest key which we will set in the manifest at build time. This removes the need to run any scripts before uploading to the webstore.
Chromoting updates will be handled in a subsequent change (TODO added).
Also made a few changes to handle the new prod_testing environment.
BUG=
Review URL: https://codereview.chromium.org/1062963002
Cr-Commit-Position: refs/heads/master@{#324067}
|
| |
|
|
|
|
|
|
|
|
| |
GCD support is off by default.
BUG=470744
Review URL: https://codereview.chromium.org/1007153003
Cr-Commit-Position: refs/heads/master@{#322430}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
app-streaming builds, cleanup definition of those variables.
Move variables to common include file.
Tested by building in a shell with only
GYP_DEFINES': 'component=shared_library use_goma=1
BUG=
Review URL: https://codereview.chromium.org/1031203004
Cr-Commit-Position: refs/heads/master@{#322321}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was an unfortunate bug that swallowed Java stacks.
Issues were discovered when Java stacks started surfacing:
https://codereview.chromium.org/476453002/
So change the way remoting is built. It doesn't need to be
built on all bots by default: they have undefined Java versions
and likely weren't working before (and shouldn't differ).
Instead, run when run_jscompile=1 is defined in GYP:
export GYP_DEFINES=run_jscompile=1 && build/gyp_chromium
# or add in ~/.gyp/includes.gypi or $SRC/../chromium.gyp_env
# or build/gyp_chromium -Drun_jscompile=1
and on the Closure Compilation Linux FYI bot:
http://build.chromium.org/p/chromium.fyi/builders/Closure%20Compilation%20Linux
This also fixes some GYP inputs problems (if I changed compile_js.gypi or
other things in remoting/ ninja wouldn't rebuild anything).
R=jamiewalch@chromium.org
BUG=none
TEST=green bots, remoting runs on Closure Compliation Linux FYI bot
Review URL: https://codereview.chromium.org/1037613002
Cr-Commit-Position: refs/heads/master@{#322193}
|
|
|
Default vars (like run_jscompile) should only be defined in one place.
This cl adds remoting_options.gypi so that the variables can be used
by both DesktopRemoting and AppRemoting gyp files.
BUG=
Review URL: https://codereview.chromium.org/974673002
Cr-Commit-Position: refs/heads/master@{#318838}
|
