C++ bindings: separate out serialization source set, have "mojom" targets optionally use serializat…

examples/serialization/serialization.mojom

Index: examples/serialization/serialization.mojom
diff --git a/mojo/public/interfaces/bindings/tests/test_included_unions.mojom b/examples/serialization/serialization.mojom
similarity index 53%
copy from mojo/public/interfaces/bindings/tests/test_included_unions.mojom
copy to examples/serialization/serialization.mojom
index 5c08681eda089a440f67369fadd07b6a4a0bd00f..5a431ea9337a572992f11355245a754ce72d7132 100644
--- a/mojo/public/interfaces/bindings/tests/test_included_unions.mojom
+++ b/examples/serialization/serialization.mojom
@@ -1,9 +1,11 @@
 // Copyright 2015 The Chromium Authors. All rights reserved.
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
+// Use of this source code is governed by a BSD-style license that can be found
+// in the LICENSE file.
 
-module mojo.test;
+module mojo.examples;

[viettrungluu, 2015/10/20 23:54:37]

I don't think you need to put this in the mojo module.

(Or even in the examples module, for that matter.)

[vardhan, 2015/10/21 19:29:38]

All the examples I checked (echo, device_name, indirect_service,
keyboard_client) are atleast in an examples {} namespace.

Any reason why this should be in global namespace vs. example?
(I'll move it out of the mojo namespace though)

 
-union IncludedUnion {
-  int8 a;
+struct MyStruct {
+  int32 a;
+  float b;
+  string c;
 };