commit | f0500887d4b5fc22ae9ba743f0450240a006628a | [log] [tgz] |
---|---|---|
author | Alex Fandrianto <alexfandrianto@google.com> | Thu Mar 03 11:00:48 2016 -0800 |
committer | Jungho Ahn <jhahn@google.com> | Fri Mar 04 01:12:15 2016 +0000 |
tree | b1f510daf2724f31734d7fce4835d37f3a072f6c | |
parent | 6141b217a698c73ce7b12b9e0586b10f72892b96 [diff] |
TBR: v23proxy: Adjust implementation for mojo v8 Note: Test is unlikely to pass. Go and Dart have incompatible mojom type implementations with the current cut of mojov8 There are 2 issues: - dart pubspec.yaml are at mojo_sdk 0.2.16, but we're probably going to go 0.2.18 after https://codereview.chromium.org/1753013002/ and a followup are submitted. - test for vdltype to mojom type had the map test partially disabled MultiPart: 3/3 Change-Id: I4d3df772aeba8ef085460227ea1fca31e1bd35cd
This repository implements the proposal outlined here that enables communication between Mojo applications on different devices.
You must have the jiri
tool installed with the base
and mojo
v23-profiles.
To update v23proxy to the latest version of mojo, you will need to also have the mojo-dev
profile.
You must always make build
first. (The Makefile is not very good currently.)
make build
ANDROID=1 make build
The commands above build the .mojo
shared library that can be run by mojo shells. For example:
make start-v23proxy
HOME=/tmp make ARGS="{see Makefile}" start-echo-client
You can also run these with Android devices. Use an ANDROID={N}
prefix to run on the Nth
Android device connected to your machine. N
must be a positive integer.
Note: To run these examples, the devices used must run mojo_shell on the same local network.
Prefix all commands with USE_MOJO_DEV_PROFILE=1
in order to run with the mojo-dev
profile instead of mojo
.