轉自：https://www.cnblogs.com/ghj1976/p/5435565.html
僅作個人備份，瀏覽請看原文
命令參數
$ protoc -help
Usage: protoc [OPTION] PROTO_FILES
Parse PROTO_FILES and generate output based on the options given:
-IPATH, --proto_path=PATH Specify the directory in which to search for
imports. May be specified multiple times;
directories will be searched in order. If not
given, the current working directory is used.
--version Show version info and exit.
-h, --help Show this text and exit.
--encode=MESSAGE_TYPE Read a text-format message of the given type
from standard input and write it in binary
to standard output. The message type must
be defined in PROTO_FILES or their imports.
--decode=MESSAGE_TYPE Read a binary message of the given type from
standard input and write it in text format
to standard output. The message type must
be defined in PROTO_FILES or their imports.
--decode_raw Read an arbitrary protocol message from
standard input and write the raw tag/value
pairs in text format to standard output. No
PROTO_FILES should be given when using this
flag.
-oFILE, Writes a FileDescriptorSet (a protocol buffer,
--descriptor_set_out=FILE defined in descriptor.proto) containing all of
the input files to FILE.
--include_imports When using --descriptor_set_out, also include
all dependencies of the input files in the
set, so that the set is self-contained.
--include_source_info When using --descriptor_set_out, do not strip
SourceCodeInfo from the FileDescriptorProto.
This results in vastly larger descriptors that
include information about the original
location of each decl in the source file as
well as surrounding comments.
--dependency_out=FILE Write a dependency output file in the format
expected by make. This writes the transitive
set of input file paths to FILE
--error_format=FORMAT Set the format in which to print errors.
FORMAT may be 'gcc' (the default) or 'msvs'
(Microsoft Visual Studio format).
--print_free_field_numbers Print the free field numbers of the messages
defined in the given proto files. Groups share
the same field number space with the parent
message. Extension ranges are counted as
occupied fields numbers.
--plugin=EXECUTABLE Specifies a plugin executable to use.
Normally, protoc searches the PATH for
plugins, but you may specify additional
executables not in the path using this flag.
Additionally, EXECUTABLE may be of the form
NAME=PATH, in which case the given plugin name
is mapped to the given executable even if
the executable's own name differs.
--cpp_out=OUT_DIR Generate C++ header and source.
--csharp_out=OUT_DIR Generate C# source file.
--java_out=OUT_DIR Generate Java source file.
--javanano_out=OUT_DIR Generate Java Nano source file.
--js_out=OUT_DIR Generate JavaScript source.
--objc_out=OUT_DIR Generate Objective C header and source.
--python_out=OUT_DIR Generate Python source file.
--ruby_out=OUT_DIR Generate Ruby source file.
例子
1. Java 文件生成
$ protoc --java_out=./java/ ./proto/helloworld.proto
protoc 的命令格式爲 protoc [OPTION] PROTO_FILES （最後是待編譯的 proto文件）
--java_out 爲輸出java代碼的目錄，這裏指定的是 ./java/ 目錄。
隨後我們指定了proto文件的位置 ./proto/helloworld.proto 。
執行上述命令，我們就 ./java/ 目錄下就產生了對應的 java文件。
2. go 文件生成
下面這幾種方式生成都可以：
$ protoc --go_out=./go/ ./proto/helloworld.proto
跟上面Java的生成完全一樣，只不過這次是讓生成 go 的代碼。
$ protoc --proto_path=/home/www/go/src --go_out=. /home/www/go/src/protoTest/common.proto
指定了源目錄
$ protoc --go_out=./go/ -I proto ./proto/helloworld.proto
這次多了一個參數 -I ，簡單來說，就是如果多個proto文件之間有互相依賴，生成某個proto文件時，需要import其他幾個proto文件，這時候就要用-I來指定搜索目錄。如果沒有指定 –I 參數，則在當前目錄進行搜索。
上面兩種方法產生的目錄如下圖， –I 參數起作用了後，生成目錄少了一級：
