ADD: added new version of protobuf
This commit is contained in:
Henry Winkel
@@ -5,31 +5,26 @@ Copyright 2008 Google Inc.
|
||||
|
||||
https://developers.google.com/protocol-buffers/
|
||||
|
||||
CMake Installation
|
||||
-----------------------
|
||||
|
||||
To compile or install protobuf from source using CMake, see
|
||||
[cmake/README.md](../cmake/README.md).
|
||||
|
||||
C++ Protobuf - Unix
|
||||
C++ Installation - Unix
|
||||
-----------------------
|
||||
|
||||
To build protobuf from source, the following tools are needed:
|
||||
|
||||
* bazel
|
||||
* git
|
||||
* autoconf
|
||||
* automake
|
||||
* libtool
|
||||
* make
|
||||
* g++
|
||||
* unzip
|
||||
|
||||
On Ubuntu/Debian, for example, you can install them with:
|
||||
On Ubuntu/Debian, you can install them with:
|
||||
|
||||
sudo apt-get install g++ git bazel
|
||||
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. See https://bazel.build/install for further
|
||||
instructions on installing Bazel, or to build from source using CMake, see
|
||||
[cmake/README.md](../cmake/README.md).
|
||||
install them before proceeding.
|
||||
|
||||
To get the source, download the release .tar.gz or .zip package in the
|
||||
To get the source, download one of the release .tar.gz or .zip packages in the
|
||||
release page:
|
||||
|
||||
https://github.com/protocolbuffers/protobuf/releases/latest
|
||||
@@ -46,23 +41,79 @@ if you are using a release .tar.gz or .zip package):
|
||||
git clone https://github.com/protocolbuffers/protobuf.git
|
||||
cd protobuf
|
||||
git submodule update --init --recursive
|
||||
./autogen.sh
|
||||
|
||||
To build the C++ Protocol Buffer runtime and the Protocol Buffer compiler
|
||||
(protoc) execute the following:
|
||||
To build and install the C++ Protocol Buffer runtime and the Protocol
|
||||
Buffer compiler (protoc) execute the following:
|
||||
|
||||
bazel build :protoc :protobuf
|
||||
|
||||
The compiler can then be installed, for example on Linux:
|
||||
./configure
|
||||
make -j$(nproc) # $(nproc) ensures it uses all cores for compilation
|
||||
make check
|
||||
sudo make install
|
||||
sudo ldconfig # refresh shared library cache.
|
||||
|
||||
cp bazel-bin/protoc /usr/local/bin
|
||||
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 more usage information on Bazel, please refer to http://bazel.build.
|
||||
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 setup a Bazel
|
||||
WORKSPACE that's hooked up to the protobuf repository and loads its
|
||||
dependencies. For an example, see [WORKSPACE](../examples/WORKSPACE).
|
||||
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**
|
||||
|
||||
@@ -76,16 +127,64 @@ 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 bazel
|
||||
sudo /opt/local/bin/port install autoconf automake libtool
|
||||
|
||||
Alternative for Homebrew users:
|
||||
|
||||
brew install bazel
|
||||
brew install autoconf automake libtool
|
||||
|
||||
Then follow the Unix instructions above.
|
||||
|
||||
**Note for cross-compiling**
|
||||
|
||||
C++ Protobuf - Windows
|
||||
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
|
||||
@@ -121,10 +220,10 @@ 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 in your `cc_binary` Bazel rules
|
||||
by specifying:
|
||||
using static linkage. You can configure this package to install
|
||||
static libraries only using:
|
||||
|
||||
linkstatic=True
|
||||
./configure --disable-shared
|
||||
|
||||
Usage
|
||||
-----
|
||||
|
||||
Reference in New Issue
Block a user