Searched refs:protoc (Results 1 – 23 of 23) sorted by relevance
20 protoc = "../src/protoc" variable22 protoc = "../src/protoc.exe" variable24 protoc = find_executable("protoc") variable42 if protoc == None:48 protoc_command = [ protoc, "-I../src", "-I.", "--python_out=.", source ]
12 Protocol Compiler (protoc). If you downloaded this package from PyPI40 3) Build the C++ code, or install a binary distribution of protoc. If44 $ protoc --version
9 Buffer compiler (protoc) execute the following:76 The makefiles normally invoke the protoc executable that they just77 built in order to build tests. When cross-compiling, the protoc79 you must build a copy of protoc for the host machine first, then use80 the --with-protoc option to tell configure to use it instead. For83 ./configure --with-protoc=protoc85 This will use the installed protoc (found in your $PATH) instead of91 ./configure --with-protoc=../host/src/protoc93 Either way, you must make sure that the protoc executable you use144 Buffer compiler (protoc), which is part of the C++ package.
30 make $@ protoc &&31 ./protoc --cpp_out=dllexport_decl=LIBPROTOBUF_EXPORT:. google/protobuf/descriptor.proto && \32 ./protoc --cpp_out=dllexport_decl=LIBPROTOC_EXPORT:. google/protobuf/compiler/plugin.proto
38 AC_ARG_WITH([protoc], optwith39 [AS_HELP_STRING([--with-protoc=COMMAND],40 …[use the given protoc command instead of building a new one when building tests (useful for cross-…122 # No argument given. Use system protoc.123 PROTOC=protoc130 # is a nested package and --with-protoc was actually given on the outer
17 protoc25 * If the output location ends in .zip or .jar, protoc will write its output27 protoc --java_out=myproto_srcs.jar --python_out=myproto.zip myproto.proto122 * Cross-compiling should now be possible using the --with-protoc option to125 protoc163 * For each enum type Foo, protoc will generate functions:227 protoc237 the file), protoc incorrectly thought that the file was under ".", because334 protoc340 other than C++: just run protoc as a background process and have it output
13 Initially the protoc compiler is not integrated into the Android build system
50 src/protoc
55 vsprojects/protoc.vcproj \
242 vsprojects/protoc.vcproj \
1503 --with-protoc=COMMAND use the given protoc command instead of building a16439 PROTOC=protoc
16 2) Build the C++ code, or obtain a binary distribution of protoc. If20 $ protoc --version22 You will need to place the protoc executable in ../src. (If you72 1) Build the C++ code, or obtain a binary distribution of protoc. If76 $ protoc --version81 2) Invoke protoc to build DescriptorProtos.java:83 $ protoc --java_out=src/main/java -I../src \118 To generate code for the MICRO_RUNTIME invoke protoc with204 Assuming you've only compiled and not installed protoc and208 ../src/protoc --javamicro_out=. src/test/proto/simple-data.proto[all …]
36 // protoc (aka the Protocol Compiler) can be extended via plugins. A plugin is44 // plugin should be named "protoc-gen-$NAME", and will then be used when the45 // flag "--${NAME}_out" is passed to protoc.65 // protoc guarantees that all proto_files will be written after70 // is not similarly optimized on protoc's end -- it will store all fields in82 // problem in protoc itself -- such as the input CodeGeneratorRequest being96 // and allows the generated text to be streamed back to protoc so that large98 // this writing protoc does not optimize for this -- it will read the entire134 // inserts into it must both run as part of a single invocatino of protoc.
50 ./protoc --cpp_out=testzip.zip --python_out=testzip.zip --java_out=testzip.jar \
12 #error This file was generated by a newer version of protoc which is17 #error This file was generated by an older version of protoc which is19 #error regenerate this file with a newer version of protoc.
36 '<(PRODUCT_DIR)/<(EXECUTABLE_PREFIX)protoc<(EXECUTABLE_SUFFIX)',44 '<(PRODUCT_DIR)/<(EXECUTABLE_PREFIX)protoc<(EXECUTABLE_SUFFIX)',54 '../../../../third_party/protobuf/protobuf.gyp:protoc#host',
21 protoc --cpp_out=. --java_out=. --python_out=. addressbook.proto
201 bin_PROGRAMS = protoc program278 unittest_proto_middleman: protoc$(EXEEXT) $(protoc_inputs)279 …oldpwd=`pwd` && ( cd $(srcdir) && $$oldpwd/protoc$(EXEEXT) -I. --cpp_out=$$oldpwd $(protoc_inputs)…294 check_PROGRAMS = protoc protobuf-test protobuf-lazy-descriptor-test \ program
39 bin_PROGRAMS = protoc$(EXEEXT)40 check_PROGRAMS = protoc$(EXEEXT) protobuf-test$(EXEEXT) \894 protoc$(EXEEXT): $(protoc_OBJECTS) $(protoc_DEPENDENCIES) 895 @rm -f protoc$(EXEEXT)2863 @USE_EXTERNAL_PROTOC_FALSE@unittest_proto_middleman: protoc$(EXEEXT) $(protoc_inputs)2864 @USE_EXTERNAL_PROTOC_FALSE@ oldpwd=`pwd` && ( cd $(srcdir) && $$oldpwd/protoc$(EXEEXT) -I. --cpp_ou…
11 Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "protoc", "protoc.vcproj", "{1738D5F6-ED1E-47E0…
18 7) Copy protoc.exe wherever you put build tools (probably somewhere in your