Protocol Buffers - Google's data interchange format
===================================================
[![Build Status](https://travis-ci.org/google/protobuf.svg?branch=master)](https://travis-ci.org/google/protobuf) [![Build status](https://ci.appveyor.com/api/projects/status/73ctee6ua4w2ruin?svg=true)](https://ci.appveyor.com/project/protobuf/protobuf)
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
C++ Installation - Unix
-----------------------
To build protobuf from source, the following tools are needed:
* autoconf
* automake
* libtool
* curl (used to download gmock)
* make
* g++
* unzip
On Ubuntu, you can install them with:
$ sudo apt-get install autoconf automake libtool curl make g++ unzip
On other platforms, please use the corresponding package managing tool to
install them before proceeding.
If you get the source from github, you need to generate the configure script
first:
$ ./autogen.sh
This will download gmock source (which is used for C++ Protocol Buffer
unit-tests) to the current directory and run automake, autoconf, etc.
to generate the configure script and various template makefiles.
You can skip this step if you are using a release package (which already
contains gmock and the configure script).
To build and install the C++ Protocol Buffer runtime and the Protocol
Buffer compiler (protoc) execute the following:
$ ./configure
$ make
$ make check
$ sudo make install
$ sudo ldconfig # refresh shared library cache.
If "make check" fails, you can still install, but it is likely that
some features of this library will not work correctly on your system.
Proceed at your own risk.
For advanced usage information on configure and make, please refer to the
autoconf documentation:
http://www.gnu.org/software/autoconf/manual/autoconf.html#Running-configure-Scripts
**Hint on install location**
By default, the package will be installed to /usr/local. However,
on many platforms, /usr/local/lib is not part of LD_LIBRARY_PATH.
You can add it, but it may be easier to just install to /usr
instead. To do this, invoke configure as follows:
./configure --prefix=/usr
If you already built the package with a different prefix, make sure
to run "make clean" before building again.
**Compiling dependent packages**
To compile a package that uses Protocol Buffers, you need to pass
various flags to your compiler and linker. As of version 2.2.0,
Protocol Buffers integrates with pkg-config to manage this. If you
have pkg-config installed, then you can invoke it to get a list of
flags like so:
pkg-config --cflags protobuf # print compiler flags
pkg-config --libs protobuf # print linker flags
pkg-config --cflags --libs protobuf # print both
For example:
c++ my_program.cc my_proto.pb.cc `pkg-config --cflags --libs protobuf`
Note that packages written prior to the 2.2.0 release of Protocol
Buffers may not yet integrate with pkg-config to get flags, and may
not pass the correct set of flags to correctly link against
libprotobuf. If the package in question uses autoconf, you can
often fix the problem by invoking its configure script like:
configure CXXFLAGS="$(pkg-config --cflags protobuf)" \
LIBS="$(pkg-config --libs protobuf)"
This will force it to use the correct flags.
If you are writing an autoconf-based package that uses Protocol
Buffers, you should probably use the PKG_CHECK_MODULES macro in your
configure script like:
PKG_CHECK_MODULES([protobuf], [protobuf])
See the pkg-config man page for more info.
If you only want protobuf-lite, substitute "protobuf-lite" in place
of "protobuf" in these examples.
**Note for Mac users**
For a Mac system, Unix tools are not available by default. You will first need
to install Xcode from the Mac AppStore and then run the following command from
a terminal:
$ sudo xcode-select --install
To install Unix tools, you can install "port" following the instructions at
https://www.macports.org . This will reside in /opt/local/bin/port for most
Mac installations.
$ sudo /opt/local/bin/port install autoconf automake libtool
Then follow the Unix instructions above.
**Note for cross-compiling**
The makefiles normally invoke the protoc executable that they just
built in order to build tests. When cross-compiling, the protoc
executable may not be executable on the host machine. In this case,
you must build a copy of protoc for the host machine first, then use
the --with-protoc option to tell configure to use it instead. For
example:
./configure --with-protoc=protoc
This will use the installed protoc (found in your $PATH) instead of
trying to execute the one built during the build process. You can
also use an executable that hasn't been installed. For example, if
you built the protobuf package for your host machine in ../host,
you might do:
./configure --with-protoc=../host/src/protoc
Either way, you must make sure that the protoc executable you use
has the same version as the protobuf source code you are trying to
use it with.
**Note for Solaris users**
Solaris 10 x86 has a bug that will make linking fail, complaining
about libstdc++.la being invalid. We have included a work-around
in this package. To use the work-around, run configure as follows:
./configure LDFLAGS=-L$PWD/src/solaris
See src/solaris/libstdc++.la for more info on this bug.
**Note for HP C++ Tru64 users**
To compile invoke configure as follows:
./configure CXXFLAGS="-O -std ansi -ieee -D__USE_STD_IOSTREAM"
Also, you will need to use gmake instead of make.
**Note for AIX users**
Compile using the IBM xlC C++ compiler as follows:
./configure CXX=xlC
Also, you will need to use GNU `make` (`gmake`) instead of AIX `make`.
C++ Installation - Windows
--------------------------
If you only need the protoc binary, you can download it from the release
page:
https://github.com/google/protobuf/releases
In the downloads section, download the zip file protoc-$VERSION-win32.zip.
It contains the protoc binary as well as public proto files of protobuf
library.
To build from source using Microsoft Visual C++, see [cmake/README.md](../cmake/README.md).
To build from source using Cygwin or MinGW, follow the Unix installation
instructions, above.
Binary Compatibility Warning
----------------------------
Due to the nature of C++, it is unlikely that any two versions of the
Protocol Buffers C++ runtime libraries will have compatible ABIs.
That is, if you linked an executable against an older version of
libprotobuf, it is unlikely to work with a newer version without
re-compiling. This problem, when it occurs, will normally be detected
immediately on startup of your app. Still, you may want to consider
using static linkage. You can configure this package to install
static libraries only using:
./configure --disable-shared
Usage
-----
The complete documentation for Protocol Buffers is available via the
web at:
https://developers.google.com/protocol-buffers/
没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
收起资源包目录
grpc windows vs2015 (884个子文件)
Makefile.am 51KB
bad_utf8_string 3B
unittest.pb.cc 1.77MB
descriptor.pb.cc 612KB
unittest_lite.pb.cc 529KB
map_unittest.pb.cc 435KB
json_format_proto3.pb.cc 403KB
default_value.pb.cc 401KB
unittest_proto3_arena.pb.cc 378KB
unittest_well_known_types.pb.cc 355KB
unittest_custom_options.pb.cc 354KB
unittest_no_arena.pb.cc 327KB
unittest_proto3_arena_lite.pb.cc 322KB
books.pb.cc 311KB
unittest_proto3_lite.pb.cc 287KB
cpp_test_bad_identifiers.pb.cc 286KB
map_lite_unittest.pb.cc 269KB
descriptor_unittest.cc 242KB
descriptor.cc 241KB
unittest_no_field_presence.pb.cc 219KB
test_util.cc 183KB
map_proto2_unittest.pb.cc 178KB
maps.pb.cc 161KB
cpp_message.cc 138KB
type.pb.cc 116KB
js_generator.cc 114KB
map_test.cc 110KB
parser_unittest.cc 106KB
field_mask.pb.cc 99KB
message_differencer_unittest.cc 97KB
wrappers.pb.cc 92KB
test_util_lite.cc 91KB
generated_message_reflection.cc 87KB
strutil.cc 81KB
message_differencer_unittest.pb.cc 79KB
map_test_util.cc 77KB
protostream_objectwriter_test.cc 76KB
unittest_mset.pb.cc 75KB
cpp_unittest.cc 74KB
parser.cc 74KB
extension_set.cc 73KB
api.pb.cc 73KB
text_format.cc 69KB
plugin.pb.cc 67KB
unittest_preserve_unknown_enum.pb.cc 66KB
command_line_interface.cc 65KB
oneofs.pb.cc 63KB
message_differencer.cc 63KB
command_line_interface_unittest.cc 60KB
text_format_unittest.cc 54KB
python_generator.cc 54KB
struct.pb.cc 54KB
extension_set_unittest.cc 53KB
objectivec_helpers.cc 53KB
java_message.cc 53KB
arena_unittest.cc 50KB
coded_stream_unittest.cc 48KB
repeated_field_unittest.cc 47KB
java_message_field.cc 46KB
wire_format_unittest.cc 44KB
wire_format.cc 43KB
protostream_objectwriter.cc 42KB
protostream_objectsource.cc 41KB
default_value_test.pb.cc 39KB
cpp_message_field.cc 39KB
java_message_lite.cc 39KB
tokenizer.cc 38KB
tokenizer_unittest.cc 38KB
cpp_file.cc 38KB
java_string_field.cc 36KB
generated_message_reflection_unittest.cc 36KB
java_enum_field.cc 35KB
cpp_string_field.cc 35KB
javanano_primitive_field.cc 35KB
java_enum_field_lite.cc 35KB
unittest_preserve_unknown_enum2.pb.cc 34KB
java_message_field_lite.cc 34KB
anys.pb.cc 34KB
java_primitive_field_lite.cc 33KB
java_map_field_lite.cc 32KB
dynamic_message.cc 32KB
java_string_field_lite.cc 32KB
protostream_objectsource_test.cc 32KB
strutil_unittest.cc 32KB
zero_copy_stream_unittest.cc 31KB
coded_stream.cc 31KB
java_primitive_field.cc 31KB
extension_set_heavy.cc 30KB
unittest_drop_unknown_fields.pb.cc 30KB
unittest_arena.pb.cc 30KB
repeated_field_reflection_unittest.cc 29KB
unittest_optimize_for.pb.cc 29KB
java_map_field.cc 28KB
java_lazy_message_field.cc 28KB
unittest_mset_wire_format.pb.cc 28KB
proto_writer.cc 28KB
lite_unittest.cc 27KB
field_mask_util_test.cc 26KB
java_lazy_message_field_lite.cc 26KB
java_message_builder.cc 26KB
共 884 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9
jnpher
- 粉丝: 215
- 资源: 44
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
- 1
- 2
- 3
- 4
- 5
前往页