#Open arena pure server code

The protocol buffer compiler generates a class called Foo, which publicly derives from google::protobuf::Message. For example, given the package declaration:Īll declarations in the file will reside in the foo::bar namespace. proto file contains a package declaration, the entire contents of the file will be placed in a corresponding C++ namespace. The compiler will automatically create the directory build/gen/bar if necessary, but it will not create build or build/gen they must already exist. The compiler will read the files src/foo.proto and src/bar/baz.proto and produce four output files: build/gen/foo.pb.h, build/gen/foo.pb.cc, build/gen/bar/baz.pb.h, build/gen/bar/baz.pb.cc. Protoc -proto_path=src -cpp_out=build/gen src/foo.proto src/bar/baz.proto So, for example, let's say you invoke the compiler as follows: The proto path (specified with the -proto_path= or -I command-line flag) is replaced with the output path (specified with the -cpp_out= flag).pb.cc for the header or implementation file, respectively. The names of the output files are computed by taking the name of the. The compiler creates a header file and an implementation file for each. The parameter to the -cpp_out= option is the directory where you want the compiler to write your C++ output. The protocol buffer compiler produces C++ output when invoked with the -cpp_out= command-line flag. You should read the proto2 language guide and/or proto3 language guide before reading this document.

#Open arena pure server code

Any differences between proto2 and proto3 generated code are highlighted - note that these differences are in the generated code as described in this document, not the base message classes/interfaces, which are the same in both versions. This page describes exactly what C++ code the protocol buffer compiler generates for any given protocol definition.