diff options
author | weitaosu@chromium.org <weitaosu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-01 11:43:40 +0000 |
---|---|---|
committer | weitaosu@chromium.org <weitaosu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-01 11:43:40 +0000 |
commit | e6791fd4692027e86635adf84b918757eebade45 (patch) | |
tree | a2d257839cc86271b5a45d7cc97a55cfb1800d19 /cc | |
parent | efc897f7d4133bc9e119d29a2878375abc07e4fd (diff) | |
download | chromium_src-e6791fd4692027e86635adf84b918757eebade45.zip chromium_src-e6791fd4692027e86635adf84b918757eebade45.tar.gz chromium_src-e6791fd4692027e86635adf84b918757eebade45.tar.bz2 |
It2Me native messaging: GYP and source refactoring
1. Add "me2me" to the names of all the me2me specific GYP targets and source files. This makes it easier for my next CL that will add the It2Me native messaging host component.
2. Create a remoting_native_messaging_base GYP target that contains the common native messaging plumbing code shared between remoting_core, remoting_me2me_native_messaging_host and the to-be-created remoting_it2me_native_messaging_host.
3. Clean up some dependencies in remoting.gyp: e.g. the native messaging manifest should be depended on by the archive targets, not the native messaging host binary targets.
4. Rename It2MeImpl to It2MeHost.
BUG=309844
Review URL: https://codereview.chromium.org/49113003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232331 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc')
0 files changed, 0 insertions, 0 deletions