Home
last modified time | relevance | path

Searched refs:protoc (Results 1 – 25 of 78) sorted by relevance

1234

/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/java/compatibility_tests/v2.5.0/
Dtest.sh20 …_VERSION_PROTOC=https://github.com/xfxyjwf/protobuf-compiler-release/raw/master/v2.5.0/linux/protoc
24 …OLD_VERSION_PROTOC=http://repo1.maven.org/maven2/com/google/protobuf/protoc/2.6.1-build2/protoc-2.…
28 …OLD_VERSION_PROTOC=http://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0-beta-1/protoc-3.…
32 …OLD_VERSION_PROTOC=http://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0-beta-2/protoc-3.…
36 …OLD_VERSION_PROTOC=http://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0-beta-3/protoc-3.…
40 …OLD_VERSION_PROTOC=http://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0-beta-4/protoc-3.…
54 [ -f ../../../src/protoc ] || {
75 wget $OLD_VERSION_PROTOC -O protoc
76 chmod +x protoc
86 -Dprotoc.path=$(pwd)/protoc \
[all …]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/protoc-artifacts/
DREADME.md1 # Build scripts that publish pre-compiled protoc artifacts
2 ``protoc`` is the compiler for ``.proto`` files. It generates language bindings
5 Because ``protoc`` is a native executable, the scripts under this directory
6 build and publish a ``protoc`` executable (a.k.a. artifact) to Maven
8 would not need to compile and install ``protoc`` for their systems.
11 The version of the ``protoc`` artifact must be the same as the version of the
15 The name of a published ``protoc`` artifact is in the following format:
16 ``protoc-<version>-<os>-<arch>.exe``, e.g., ``protoc-3.0.0-alpha-3-windows-x86_64.exe``.
37 The following command will install the ``protoc`` artifact to your local Maven repository.
44 system properties. It's possible to build a protoc binary for an architecture
[all …]
Dbuild-zip.sh10 This script will download pre-built protoc binaries from maven repository
14 dist/protoc-<VERSION_NUMBER>-win32.zip
15 dist/protoc-<VERSION_NUMBER>-osx-x86_32.zip
16 dist/protoc-<VERSION_NUMBER>-osx-x86_64.zip
17 dist/protoc-<VERSION_NUMBER>-linux-x86_32.zip
18 dist/protoc-<VERSION_NUMBER>-linux-x86_64.zip
/frameworks/base/tools/streaming_proto/
DAndroid.bp18 // Build the host executable: protoc-gen-javastream
21 name: "protoc-gen-stream-defaults",
36 name: "protoc-gen-javastream",
41 defaults: ["protoc-gen-stream-defaults"],
45 name: "protoc-gen-cppstream",
50 defaults: ["protoc-gen-stream-defaults"],
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/csharp/
Dgenerate_protos.sh16 if [ -x cmake/build/Debug/protoc.exe ]; then
17 PROTOC=cmake/build/Debug/protoc.exe
18 elif [ -x cmake/build/Release/protoc.exe ]; then
19 PROTOC=cmake/build/Release/protoc.exe
20 elif [ -x src/protoc ]; then
21 PROTOC=src/protoc
D.gitignore10 mono/protoc
30 lib/protoc.exe
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/python/
Dsetup.py25 protoc = os.environ['PROTOC'] variable
27 protoc = "../src/protoc" variable
29 protoc = "../src/protoc.exe" variable
31 protoc = "../vsprojects/Debug/protoc.exe" variable
33 protoc = "../vsprojects/Release/protoc.exe" variable
35 protoc = find_executable("protoc") variable
68 if protoc is None:
74 protoc_command = [ protoc, "-I../src", "-I.", "--python_out=.", source ]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/benchmarks/
DMakefile.am61 protoc_middleman: $(top_srcdir)/src/protoc$(EXEEXT) $(benchmarks_protoc_inputs) $(well_known_type_p…
62 …oldpwd=`pwd` && ( cd $(srcdir) && $$oldpwd/../src/protoc$(EXEEXT) -I. -I$(top_srcdir)/src --cpp_ou…
65 protoc_middleman2: $(top_srcdir)/src/protoc$(EXEEXT) $(benchmarks_protoc_inputs_proto2) $(well_know…
66 …oldpwd=`pwd` && ( cd $(srcdir) && $$oldpwd/../src/protoc$(EXEEXT) -I. -I$(top_srcdir)/src --cpp_ou…
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/
DREADME.md25 the [C++ Installation Instructions](src/README.md) to install protoc along
34 zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary
40 …/repo1.maven.org/maven2/com/google/protobuf/protoc/](http://repo1.maven.org/maven2/com/google/prot…
44 or you are using C++, it's recommended to build your own protoc binary from
47 If you would like to build protoc binary from source, see the [C++ Installation
59 | C++ (include C++ runtime and protoc) | [src](src) |
Dprotobuf.bzl66 args += ["--plugin=protoc-gen-grpc=" + ctx.executable.grpc_cpp_plugin.path]
74 executable=ctx.executable.protoc,
90 "protoc": attr.label(
115 protoc="//:protoc",
133 protoc: the label of the protocol compiler to generate the sources.
158 protoc=protoc,
178 protoc=protoc,
215 cmd = "$(location :protoc) --java_out=$(@D)/wellknown.jar" +
218 tools = [":protoc"],
260 protoc="//:protoc",
[all …]
Dgenerate_descriptor_proto.sh53 make $@ protoc
59 ./protoc --cpp_out=dllexport_decl=LIBPROTOBUF_EXPORT:$TMP ${RUNTIME_PROTO_FILES[@]} && \
60 ./protoc --cpp_out=dllexport_decl=LIBPROTOC_EXPORT:$TMP google/protobuf/compiler/plugin.proto
Dconfigure.ac13 # * protoc-artifacts/pom.xml
55 AC_ARG_WITH([protoc], optwith
56 [AS_HELP_STRING([--with-protoc=COMMAND],
57 …[use the given protoc command instead of building a new one when building tests (useful for cross-…
141 # No argument given. Use system protoc.
142 PROTOC=protoc
149 # is a nested package and --with-protoc was actually given on the outer
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/js/
Dgulpfile.js9 var protoc = process.env.PROTOC || '../src/protoc'; variable
27 …exec(protoc + ' --js_out=library=testproto_libs,binary:. -I ../src -I . *.proto ../src/google/pro…
36 …exec('mkdir -p commonjs_out && ' + protoc + ' --js_out=import_style=commonjs,binary:commonjs_out -…
45 …exec('mkdir -p commonjs_out/node_modules/google-protobuf && ' + protoc + ' --js_out=import_style=c…
54 exec(protoc + ' --js_out=import_style=commonjs,binary:. -I ../src ' + wellKnownTypes.join(' '),
DREADME.md23 2. The Protocol Compiler `protoc`. This translates `.proto` files
27 (look for the `protoc-*.zip` files under **Downloads**).
36 If you want, you can compile `protoc` from source instead. To do this
40 Once you have `protoc` compiled, you can run the tests by typing:
46 # If your protoc is somewhere else than ../src/protoc, instead do this.
47 # But make sure your protoc is the same version as this (or compatible)!
48 $ PROTOC=/usr/local/bin/protoc npm test
70 $ protoc --js_out=library=myproto_libs,binary:. messages.proto base.proto
72 For Closure imports, `protoc` will generate a single output file
102 $ protoc --js_out=import_style=commonjs,binary:. messages.proto base.proto
[all …]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/src/
DREADME.md43 Buffer compiler (protoc) execute the following:
128 The makefiles normally invoke the protoc executable that they just
129 built in order to build tests. When cross-compiling, the protoc
131 you must build a copy of protoc for the host machine first, then use
132 the --with-protoc option to tell configure to use it instead. For
135 ./configure --with-protoc=protoc
137 This will use the installed protoc (found in your $PATH) instead of
143 ./configure --with-protoc=../host/src/protoc
145 Either way, you must make sure that the protoc executable you use
178 If you only need the protoc binary, you can download it from the release
[all …]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/cmake/
Dprotoc.cmake5 add_executable(protoc ${protoc_files}) target
6 target_link_libraries(protoc libprotobuf libprotoc)
Dprotobuf-module.cmake.in172 # By default have PROTOBUF_GENERATE_CPP macro pass -I to protoc
185 _protobuf_find_libraries(Protobuf_PROTOC protoc)
195 # Set the protoc Executable
196 get_target_property(Protobuf_PROTOC_EXECUTABLE protobuf::protoc
199 get_target_property(Protobuf_PROTOC_EXECUTABLE protobuf::protoc
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/docs/
Dthird_party.md11 * Action Script: https://code.google.com/p/protoc-gen-as3/
31 ….com/dart-lang/dart-protobuf (runtime) https://github.com/dart-lang/dart-protoc-plugin (code gener…
37 * Erlang: https://code.google.com/p/protoc-gen-erl/
43 * Haxe: https://github.com/Atry/protoc-gen-haxe
56 * Lua: http://code.google.com/p/protoc-gen-lua/
132 * https://github.com/sergei-ivanov/maven-protoc-plugin/
134 * http://code.google.com/p/maven-protoc-plugin/
135 * https://github.com/os72/protoc-jar-maven-plugin
136 * [Documentation generator plugin (Markdown/HTML/DocBook/...)](https://github.com/estan/protoc-gen-…
137 * [DocBook generator for .proto files](http://code.google.com/p/protoc-gen-docbook/)
[all …]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/java/
DREADME.md20 2) Build the C++ code, or obtain a binary distribution of protoc (see
25 $ protoc --version
27 You will need to place the protoc executable in ../src. (If you
68 1) Build the C++ code, or obtain a binary distribution of protoc. If
72 $ protoc --version
77 2) Invoke protoc to build DescriptorProtos.java:
79 $ protoc --java_out=core/src/main/java -I../src \
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/objectivec/DevTools/
Dcompile_testing_protos.sh32 [[ -x src/protoc ]] || \
45 src/.libs src/*.la src/protoc \
103 src/protoc \
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/ruby/
DREADME.md6 we recommend using protoc's Ruby generation support with .proto files. The
8 install protoc as well to have Ruby code generation functionality.
23 Once the gem is installed, you may or may not need `protoc`. If you write your
27 main `README` file. The version of `protoc` included in the latest release
38 # generated from my_proto_types.proto with protoc:
39 # $ protoc --ruby_out=. my_proto_types.proto
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/src/google/protobuf/
Dempty.pb.h12 #error This file was generated by a newer version of protoc which is
17 #error This file was generated by an older version of protoc which is
19 #error regenerate this file with a newer version of protoc.
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/src/google/protobuf/compiler/
Dplugin.proto36 // protoc (aka the Protocol Compiler) can be extended via plugins. A plugin is
44 // plugin should be named "protoc-gen-$NAME", and will then be used when the
45 // flag "--${NAME}_out" is passed to protoc.
70 // protoc guarantees that all proto_files will be written after
75 // is not similarly optimized on protoc's end -- it will store all fields in
87 // problem in protoc itself -- such as the input CodeGeneratorRequest being
101 // and allows the generated text to be streamed back to protoc so that large
103 // this writing protoc does not optimize for this -- it will read the entire
139 // inserts into it must both run as part of a single invocation of protoc.
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/objectivec/
Dgenerate_well_known_types.sh42 make $@ protoc
59 ./protoc --objc_out="${TMP_DIR}" ${RUNTIME_PROTO_FILES[@]}
/frameworks/opt/gamesdk/src/tuningfork/tools/validation/
Dbuild.gradle47 protoc {
49 artifact = 'com.google.protobuf:protoc:3.0.0'

1234