Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Grpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tci-gateway-module
Grpc
Commits
c70752af
Commit
c70752af
authored
10 years ago
by
Nicolas Noble
Browse files
Options
Downloads
Patches
Plain Diff
Updating build instructions in regard to protobuf.
parent
5383062d
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
INSTALL
+15
-21
15 additions, 21 deletions
INSTALL
with
15 additions
and
21 deletions
INSTALL
+
15
−
21
View file @
c70752af
...
...
@@ -14,10 +14,14 @@ A typical unix installation won't require any more steps than running:
$ make
# make install
You don't need anything else than GNU Make
and gcc
. Under a Debian
or
Ubuntu system, this should boil down to the following package:
You don't need anything else than GNU Make
, gcc and autotools
. Under a Debian
or
Ubuntu system, this should boil down to the following package
s
:
# apt-get install build-essential python-all-dev python-virtualenv
# apt-get install build-essential autoconf libtool
Building the python wrapper requires the following:
# apt-get install python-all-dev python-virtualenv
*******************************
...
...
@@ -68,33 +72,23 @@ Compiling and running grpc plain-C tests dont't require any more dependency.
Compiling and running grpc C++ tests depend on protobuf 3.0.0, gtest and
gflags. Although gflags
and protobuf are
provided in third_party, you will
need to manually
install th
ese
dependenc
ies
on your system to run these tests.
gflags. Although gflags
is
provided in third_party, you will
need to manually
install th
at
dependenc
y
on your system to run these tests.
Under a Debian or Ubuntu system, you can install the gtests and gflags packages
using apt-get:
# apt-get install libgflags-dev libgtest-dev
However, protobuf 3.0.0 isn't in a debian package yet: you'll need to compile
and install it from the sources in the third_party. Note that if you already
have the protobuf and protoc packages installed on your system, they will most
likely interfere, and you'll need to uninstall them first.
However, protobuf 3.0.0 isn't in a debian package yet, but the Makefile will
automatically try and compile the one present in third_party if you cloned the
repository recursively, and that it detects your system is lacking it.
Compiling and installing protobuf 3.0.0 requires a few more dependencies in
itself, notably the autoconf suite, curl, and unzip. If you have apt-get, you
can install these dependencies this way:
# apt-get install unzip curl autoconf libtool
itself, notably the autoconf suite. If you have apt-get, you can install
these dependencies this way:
Then, you can build and install protobuf 3.0.0:
$ cd third_party/protobuf
$ ./autogen.sh
$ ./configure
$ make
# make install
# ldconfig
# apt-get install autoconf libtool
A word on OpenSSL
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment