I guess we'll also need the bindings generator in a hypothetical C++ SDK.

sdk_build/data/cpp/cpp.sdk

 # Copyright 2016 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.
 
 # This file contains steps for "building" a C/C++ SDK. It is processed by
 # //mojo/sdk_build/build_sdk.py.
 # TODO(vtl): This isn't done yet.
 
 EXCLUDE_FILES=[".*", "*.gn", "*.gni", "PRESUBMIT.py", "*_win.*"]
-EXCLUDE_PATHS=["*/tests/"]
+EXCLUDE_PATHS=["*/tests/*"]
+
+CopyFiles("mojo/public", "third_party/mojo/public", recursive=False,
+          exclude_file_patterns=EXCLUDE_FILES)
 
 CopyFiles("mojo/public/c", "third_party/mojo/public/c", recursive=True,
           exclude_file_patterns=EXCLUDE_FILES,
           exclude_path_patterns=EXCLUDE_PATHS)
 CopyFiles("mojo/public/cpp", "third_party/mojo/public/cpp", recursive=True,
           exclude_file_patterns=EXCLUDE_FILES,
           exclude_path_patterns=EXCLUDE_PATHS+
               ["mojo/public/cpp/test_support/*"])
-CopyFiles("mojo/public", "third_party/mojo/public", recursive=False,
-          exclude_file_patterns=EXCLUDE_FILES)
+
+# For simplicity, copy all of the bindings generators, even though we really
+# only need/want C++.
+CopyFiles("mojo/public/tools/bindings", "third_party/mojo/tools/bindings",

[vardhan, 2016/02/17 22:31:08]

do we need to include the mojo/public/third_party/jinja2 dependency, or can we
just assume the builder's system has that python library installed?

(broader question:  will this spec copy enough things to run the code generator
to completion on not-our-machines?)

+          recursive=True,
+          exclude_file_patterns=EXCLUDE_FILES,
+          exclude_path_patterns=EXCLUDE_PATHS+["*/mojom_tests/*"])