Move //mojo/{public, edk} underneath //third_party

Move //mojo/{public, edk} underneath //third_party

This CL move //mojo/public and //mojo/edk to live in the following locations:
- //third_party/mojo/src/mojo/public
- //third_party/mojo/src/mojo/edk

It moves the related gypfiles from //mojo to //third_party/mojo and updates
them as necessary to account for the file moves. It also updates clients of the
mojo SDK and EDK targets in both GYP and GN. (Note that for GN, the mojo SDK
and EDK build systems are maintained in the Mojo repo and designed to be
flexible wrt the location of the SDK/EDK in a client repo, so no changes are
needed.

This CL does not update include paths to the code being moved to limit the
number of moving parts, instead relying on the include_dirs that the SDK and
EDK targets supply to their direct dependents to ensure that include paths
continue to resolve correctly.

NOPRESUBMIT=true

Committed: https://crrev.com/70fb54767b472a5edfb859e489beeeec7abdb0e4
Cr-Commit-Position: refs/heads/master@{#312129}

[blundell, 2015-01-08 16:49:48]

blundell@chromium.org changed reviewers:
+ ben@chromium.org

[blundell, 2015-01-08 16:50:03]

Hi Ben,

The Chromium side of this CL is all ready now :). This CL currently incorporates
some patches on Mojo-side code for CLs that are outstanding in that repo, but I
won't land the CL until all the relevant Mojo-side patches have landed and been
rolled into Chromium.

Here is the high-level structure of the CL:

The majority of the changes are just to ignore entirely:

- //mojo/{edk, public}: This is just deleted code.
- //mojo/services/*/public: These are changes that will not be in this CL
anymore once relevant patches land on the Mojo side.
- //third_party/mojo/src: This is just the SDK and EDK in their new locations.

Of the rest of the CL, the meat of the changes is in //third_party/mojo: these
are the Mojo gypfiles that have been updated for the new location of the SDK and
EDK, as well a LICENSE and README.chromium that are now required. The rest of
the CL is just changes to client gypfiles and BUILD.gn files of the mojo SDK and
EDK targets.

Let me know if you want to bring additional reviewing hands on deck to spread
the pain.

Thanks,

Colin

[Ben Goodger (Google), 2015-01-08 18:55:57]

lgtm

[blundell, 2015-01-19 15:32:43]

The CQ bit was checked by blundell@chromium.org

[commit-bot: I haz the power, 2015-01-19 15:33:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/814543006/100001

[blundell, 2015-01-19 15:56:17]

The CQ bit was unchecked by blundell@chromium.org

[commit-bot: I haz the power, 2015-01-19 15:57:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-19 15:57:40]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[blundell, 2015-01-19 15:59:32]

The CQ bit was checked by blundell@chromium.org

[commit-bot: I haz the power, 2015-01-19 16:00:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/814543006/100001

[commit-bot: I haz the power, 2015-01-19 17:19:15]

Committed patchset #11 (id:100001)

[commit-bot: I haz the power, 2015-01-19 17:20:10]

Patchset 11 (id:??) landed as
https://crrev.com/70fb54767b472a5edfb859e489beeeec7abdb0e4
Cr-Commit-Position: refs/heads/master@{#312129}