mojom: move mojom/mojom_tool/generated -> mojom/generated. Update consumers

mojom: move mojom/mojom_tool/generated -> mojom/generated. Update consumers

R=azani@chromium.org, rudominer@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/74e3c9d3a0cce0d8159edc5783f5aca7cfdf078d

[vardhan, 2016-04-27 23:08:13]

ptal

[rudominer, 2016-04-27 23:11:23]

bots are red. please fix.

[vardhan, 2016-04-28 00:23:50]

On 2016/04/27 23:11:23, rudominer wrote:
> bots are red. please fix.

it's because i haven't updated the 'inputs' in mojom_tool/BUILD.gn:14 -- i am
now doubting this change; i'm not sure that the `mojom_tool/` dir should always
expect/assume to live alongside a generated/ dir (otherwise mojom_tool won't
build).
what do you think?

[azani, 2016-04-28 00:34:58]

On 2016/04/28 00:23:50, vardhan wrote:
> On 2016/04/27 23:11:23, rudominer wrote:
> > bots are red. please fix.
> 
> it's because i haven't updated the 'inputs' in mojom_tool/BUILD.gn:14 -- i am
> now doubting this change; i'm not sure that the `mojom_tool/` dir should
always
> expect/assume to live alongside a generated/ dir (otherwise mojom_tool won't
> build).
> what do you think?

Well, that's not really the expectation. The expectation is that for some path
specified in GOPATH, there is a src/mojom/generated sub-directory which contains
the generated files.
This may be inconvenient, but you also can't build the mojom tool without the go
bindings libraries. So, I don't think this dependency adds any problem.

[vardhan, 2016-04-28 01:18:15]

> Well, that's not really the expectation. The expectation is that for some path
> specified in GOPATH, there is a src/mojom/generated sub-directory which
contains
> the generated files.
> This may be inconvenient, but you also can't build the mojom tool without the
go
> bindings libraries.

sorry, im a little confused: I was thinking that we would distribute the
mojo_tool/ source code at some point in some SDK that isn't mojo.git. I guess we
don't have to worry about that for now.

ptal.

[vardhan, 2016-04-28 01:18:16]

> Well, that's not really the expectation. The expectation is that for some path
> specified in GOPATH, there is a src/mojom/generated sub-directory which
contains
> the generated files.
> This may be inconvenient, but you also can't build the mojom tool without the
go
> bindings libraries.

sorry, im a little confused: I was thinking that we would distribute the
mojo_tool/ source code at some point in some SDK that isn't mojo.git. I guess we
don't have to worry about that for now.

ptal.

[rudominer, 2016-04-28 18:24:43]

lgtm

[azani, 2016-04-28 19:33:27]

lgtm

[vardhan, 2016-04-28 19:35:37]

Description was changed from

==========
mojom: move mojom/mojom_tool/generated -> mojom/generated. Update consumers

R=azani@chromium.org,rudominer@chromium.org
==========

to

==========
mojom: move mojom/mojom_tool/generated -> mojom/generated. Update consumers

R=azani@chromium.org, rudominer@chromium.org

Committed:
https://chromium.googlesource.com/external/mojo/+/74e3c9d3a0cce0d8159edc5783f...
==========

[vardhan, 2016-04-28 19:35:39]

Committed patchset #2 (id:20001) manually as
74e3c9d3a0cce0d8159edc5783f5aca7cfdf078d (presubmit successful).