Bundle the DEPS of mojom_bindings_generator.py with the public SDK.

Bundle the DEPS of mojom_bindings_generator.py with the public SDK.

The rationale for this bundling is the following:
- Every client of the public SDK will need these deps to process the mojoms in
the public SDK.
- These deps are not something that clients will already have in general (as
opposed to say a C++ compiler).
- Even if the client happens to already have these deps, by packaging the
versions that mojom_bindings_generator.py is interfaced against we make
mojom_bindings_generator.py hermetic.

Note that the versions of these modules in //third_party are left there because
there are other internal dependencies on them throughout the repo.

R=viettrungluu@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/91de5b1bc985e403666d6cb45d4ba49789192eb5

[blundell, 2014-12-11 21:33:27]

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

[blundell, 2014-12-11 21:33:34]

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

[blundell, 2014-12-11 21:34:03]

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

[blundell, 2014-12-11 21:34:53]

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

[viettrungluu, 2014-12-11 22:38:46]

Probably we can make it mojom_bindings_generator.py always use the bundled
libraries, but we can do that later. LGTM.

[blundell, 2014-12-12 07:14:06]

On 2014/12/11 22:38:46, viettrungluu wrote:
> Probably we can make it mojom_bindings_generator.py always use the bundled
> libraries, but we can do that later. LGTM.

The reason I left in the flag is so that we could preserve the usability of the
script in the contexts you mentioned (e.g., linux distros). But yeah, we could
just take it out if we don't care at this point.

[blundell, 2014-12-12 07:14:34]

Committed patchset #3 (id:40001) manually as
91de5b1bc985e403666d6cb45d4ba49789192eb5.