Home
last modified time | relevance | path

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

1234

/external/nanopb-c/tools/
Dmake_linux_package.sh22 cp $DEST/generator/nanopb_generator.py $DEST/generator/protoc-gen-nanopb.py
25 ( cd $DEST/generator; bbfreeze nanopb_generator.py protoc-gen-nanopb.py )
29 rm $DEST/generator/protoc-gen-nanopb.py
32 cp `which protoc` $DEST/generator-bin/protoc.bin
33 LIBPROTOC=$(ldd `which protoc` | grep -o '/.*libprotoc[^ ]*')
35 cat > $DEST/generator-bin/protoc << EOF
42 chmod +x $DEST/generator-bin/protoc
Dmake_mac_package.sh31 cp $DEST/generator-bin/nanopb_generator $DEST/generator-bin/protoc-gen-nanopb
34 cp `which protoc` $DEST/generator-bin/protoc.bin
35 LIBPROTOC=$(otool -L `which protoc` | grep -o '/.*libprotoc[^ ]*')
36 LIBPROTOBUF=$(otool -L `which protoc` | grep -o '/.*libprotobuf[^ ]*')
38 cat > $DEST/generator-bin/protoc << EOF
45 chmod +x $DEST/generator-bin/protoc
Dmake_windows_package.sh23 cp $DEST/generator/nanopb_generator.py $DEST/generator/protoc-gen-nanopb.py
26 ( cd $DEST/generator; bbfreeze nanopb_generator.py protoc-gen-nanopb.py )
30 rm $DEST/generator/protoc-gen-nanopb.py
45 cp `which protoc.exe` $DEST/generator-bin/
/external/nanopb-c/extra/
Dnanopb.mk22 PROTOC = $(NANOPB_DIR)/generator-bin/protoc
26 PROTOC = protoc
28 PROTOC_OPTS = --plugin=protoc-gen-nanopb=$(NANOPB_DIR)/generator/protoc-gen-nanopb.bat
30 PROTOC_OPTS = --plugin=protoc-gen-nanopb=$(NANOPB_DIR)/generator/protoc-gen-nanopb
DFindNanopb.cmake19 # NANOPB_GENERATE_CPP_APPEND_PATH - By default -I will be passed to protoc
25 # NANOPB_FOUND - Found the nanopb library (source&header files, generator tool, protoc compiler t…
30 # PROTOBUF_PROTOC_EXECUTABLE - The protoc compiler
169 # By default have NANOPB_GENERATE_CPP macro pass -I to protoc
200 # Find the protoc Executable
202 NAMES protoc
/external/protobuf/python/
Dsetup.py30 protoc = os.environ['PROTOC'] variable
32 protoc = "../src/protoc" variable
34 protoc = "../src/protoc.exe" variable
36 protoc = "../vsprojects/Debug/protoc.exe" variable
38 protoc = "../vsprojects/Release/protoc.exe" variable
40 protoc = find_executable("protoc") variable
58 if protoc == None:
64 protoc_command = [ protoc, "-I../src", "-I.", "--python_out=.", source ]
DREADME.txt12 Protocol Compiler (protoc). If you downloaded this package from PyPI
40 3) Build the C++ code, or install a binary distribution of protoc. If
44 $ protoc --version
/external/nanopb-c/generator/
Dprotoc-gen-nanopb.bat3 :: to protoc on Windows.
5 :: protoc --plugin=nanopb=..../protoc-gen-nanopb.bat --nanopb_out=dir foo.proto
7 :: Note that if you use the binary package of nanopb, the protoc
12 python "%mydir%\nanopb_generator.py" --protoc-plugin
Dprotoc-gen-nanopb13 exec python "$MYPATH/nanopb_generator.py" --protoc-plugin
/external/nanopb-c/
DREADME.txt14 1) Compile your .proto files for nanopb, using protoc.
24 Using the Protocol Buffers compiler (protoc)
26 The nanopb generator is implemented as a plugin for the Google's own protoc
32 Mac OS X version), the 'protoc' binary is included in the 'generator-bin'
35 generator-bin/protoc --nanopb_out=. myprotocol.proto
38 need to provide your own version of protoc and the Google's protobuf library.
42 protoc, you need to manually give the path to nanopb generator:
44 protoc --plugin=protoc-gen-nanopb=nanopb/generator/protoc-gen-nanopb ...
/external/webrtc/webrtc/build/
Dprotoc.gypi9 # Copied from Chromium's src/build/protoc.gypi
17 # to invoke protoc in a consistent manner. For Java-targets, see
70 'protoc': '<(PRODUCT_DIR)/<(EXECUTABLE_PREFIX)protoc<(EXECUTABLE_SUFFIX)',
72 'protoc': '<!(which protoc)',
82 '<(protoc)',
99 # Naively you'd use <(RULE_INPUT_PATH) here, but protoc requires
104 '<(protoc)',
128 '<(DEPTH)/third_party/protobuf/protobuf.gyp:protoc#host',
/external/protobuf/
DREADME.md24 Buffer compiler (protoc) execute the following:
91 The makefiles normally invoke the protoc executable that they just
92 built in order to build tests. When cross-compiling, the protoc
94 you must build a copy of protoc for the host machine first, then use
95 the --with-protoc option to tell configure to use it instead. For
98 ./configure --with-protoc=protoc
100 This will use the installed protoc (found in your $PATH) instead of
106 ./configure --with-protoc=../host/src/protoc
108 Either way, you must make sure that the protoc executable you use
159 Buffer compiler (protoc), which is part of the C++ package.
Dgenerate_descriptor_proto.sh30 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
Dconfigure.ac39 AC_ARG_WITH([protoc], optwith
40 [AS_HELP_STRING([--with-protoc=COMMAND],
41 …[use the given protoc command instead of building a new one when building tests (useful for cross-…
123 # No argument given. Use system protoc.
124 PROTOC=protoc
131 # is a nested package and --with-protoc was actually given on the outer
/external/google-breakpad/src/processor/proto/
DREADME2 using protoc from the protobuf project (http://code.google.com/p/protobuf/).
12 Running protoc:
13 protoc: error while loading shared libraries: libprotobuf.so.0: cannot open
/external/nanopb-c/generator/proto/
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.
65 // protoc guarantees that all proto_files will be written after
70 // is not similarly optimized on protoc's end -- it will store all fields in
82 // problem in protoc itself -- such as the input CodeGeneratorRequest being
96 // and allows the generated text to be streamed back to protoc so that large
98 // this writing protoc does not optimize for this -- it will read the entire
134 // inserts into it must both run as part of a single invocation of protoc.
/external/protobuf/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.
67 // protoc guarantees that all proto_files will be written after
72 // is not similarly optimized on protoc's end -- it will store all fields in
84 // problem in protoc itself -- such as the input CodeGeneratorRequest being
98 // and allows the generated text to be streamed back to protoc so that large
100 // this writing protoc does not optimize for this -- it will read the entire
136 // inserts into it must both run as part of a single invocation of protoc.
/external/cros/system_api/
Dsystem_api.gyp15 'includes': ['../../platform2/common-mk/protoc.gypi'],
44 'includes': ['../../platform2/common-mk/protoc.gypi'],
73 'includes': ['../../platform2/common-mk/protoc.gypi'],
/external/protobuf/src/google/protobuf/
DSEBS66 name = "protoc",
116 protoc = _cpp.Binary(
117 name = "protoc",
135 protoc.expand_once()
137 # We must build protoc for the host configuration to allow cross-compiling.
138 host_protoc = self.context.configured_artifact(protoc.binary, "host")
/external/google-tv-pairing-protocol/cpp/
Dconfigure.ac42 AC_PATH_PROG(PROTOC, protoc,
43 [AC_MSG_ERROR([protoc was not found in your path])])
/external/nanopb-c/tests/alltypes/
DSConscript14 # Re-encode the data using protoc, and check that the results from nanopb
15 # match byte-per-byte to the protoc output.
/external/protobuf/benchmarks/
Dreadme.txt17 1) Build protoc and the Java protocol buffer library. The examples
25 $ protoc --java_out=tmp google_size.proto google_speed.proto
/external/protobuf/java/
DREADME.txt16 2) Build the C++ code, or obtain a binary distribution of protoc. If
20 $ protoc --version
22 You will need to place the protoc executable in ../src. (If you
72 1) Build the C++ code, or obtain a binary distribution of protoc. If
76 $ protoc --version
81 2) Invoke protoc to build DescriptorProtos.java:
83 $ protoc --java_out=src/main/java -I../src \
121 To generate code for the MICRO_RUNTIME invoke protoc with
242 and the compiled protoc in the current working directory,
245 ./protoc --javamicro_out=. src/proto/simple-data-protos.proto
[all …]
/external/autotest/client/site_tests/platform_MetricsUploader/src/
DMakefile17 protoc --proto_path=$(PROTO_PATH) --python_out=$(OUT_DIR) $(PROTO_DEFS)
/external/autotest/client/site_tests/login_OwnershipApi/src/
DMakefile19 protoc --proto_path=$(PROTO_PATH) --python_out=$(OUT_DIR) $(PROTO_DEFS)

1234