Rearrange mojo/nacl files.

Rearrange mojo/nacl files.

Files that were previously generated are now checked in to make SDK and
Chromium integration easier. Files needed to build mojo apps have been
moved to //mojo/public/platform/nacl. Files needed to integrate NaCl with
Mojo (used by the NaCl content handler and Chromium) have been moved to
//nacl_bindings. This directory will be copied into the Chrome tree.
//nacl_bindings_generator contains the script for regenerating the
checked-in files. This script will likely go away when the NaCl bindings
have stabilized. //mojo/nacl is deprecated and currently contains testing
and build files specific to the Mojo repo.

BUG=401761
R=jamesr@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/b0e6d97c65a5f3b0c77c0820a40245974be25af9

[Nick Bray (chromium), 2015-02-25 19:27:15]

ncbray@chromium.org changed reviewers:
+ jamesr@chromium.org

[Nick Bray (chromium), 2015-02-25 20:24:49]

Hmmm.  I realized mojo/nacl_bindings => mojo/nacl/bindings might make sense. 
Tell me what you think.

[jamesr, 2015-02-25 20:38:22]

Why not //nacl_bindings ?

[Nick Bray (chromium), 2015-02-25 22:14:36]

PTAL

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn
File nacl_bindings/BUILD.gn (right):

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:17: rebase_path("mojo/public/c/system", ".", mojo_root),
Note: a little funky, but this seemed cleaner than going full
mojo_sdk_source_set (particularly for the executable, below).

[jamesr, 2015-02-26 00:23:22]

Seems pretty good.  2 questions below where I'm not sure exactly what's going on

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn
File nacl_bindings/BUILD.gn (right):

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:10: static_library("monacl_sel") {
do you need this to be a static_library or is source_set ok? (this'll be in
practice a thin archive i think which is functionally similar to a source set,
not really a 'thick' .a)

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:35: rebase_path("mojo/public/platform/nacl/mojo_irt.h",
".", mojo_root),
it looks like nacl_bindings is always in the same place relative to mojo/public,
so could you use a relative path here? i.e.

../mojo/public/platform/nacl/mojo_irt.h

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:38: rebase_path("mojo/public/c/system", ".", mojo_root),
and same here?

../mojo/public/c/system

[Nick Bray (chromium), 2015-02-26 01:16:02]

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn
File nacl_bindings/BUILD.gn (right):

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:10: static_library("monacl_sel") {
On 2015/02/26 00:23:22, jamesr wrote:
> do you need this to be a static_library or is source_set ok? (this'll be in
> practice a thin archive i think which is functionally similar to a source set,
> not really a 'thick' .a)

Done.

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:35: rebase_path("mojo/public/platform/nacl/mojo_irt.h",
".", mojo_root),
On 2015/02/26 00:23:22, jamesr wrote:
> it looks like nacl_bindings is always in the same place relative to
mojo/public,
> so could you use a relative path here? i.e.
> 
> ../mojo/public/platform/nacl/mojo_irt.h

Done.

https://codereview.chromium.org/955113002/diff/40001/nacl_bindings/BUILD.gn#n...
nacl_bindings/BUILD.gn:38: rebase_path("mojo/public/c/system", ".", mojo_root),
On 2015/02/26 00:23:22, jamesr wrote:
> and same here?
> 
> ../mojo/public/c/system

Done.

[jamesr, 2015-02-26 01:36:48]

lgtm

[Nick Bray (chromium), 2015-02-26 19:23:03]

Committed patchset #5 (id:80001) manually as
b0e6d97c65a5f3b0c77c0820a40245974be25af9.