Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
B
brpc
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
brpc
Commits
e1756666
Commit
e1756666
authored
Aug 24, 2017
by
gejun
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README
parent
6f08143e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
69 additions
and
30 deletions
+69
-30
README
README
+69
-30
No files found.
README
View file @
e1756666
The opensource version of baidu-rpc
# BUILD
baidu-rpc prefers static linking if possible, so that deps don't have to be installed on every machine running the code.
baidu-rpc prefers static linking if possible, so that deps don't have to be installed on every
machine running the code.
### Ubuntu/LinuxMint/WSL
**install common deps**
Including: git g++ make libssl-dev
**install gflags protobuf leveldb**
Including: libgflags-dev libprotobuf-dev libprotoc-dev protobuf-compiler libleveldb-dev
If you need to statically link leveldb, install libsnappy-dev as well.
**compile**
git clone this repo. cd into the repo and run: sh config_brpc.sh --headers=/usr/include --libs=/usr/lib
**run example**
cd into example/echo_c++, make, run echo_server and echo_client
**run examples with cpu/heap profilers**
Install libgoogle-perftools-dev and re-run config_brpc.sh before compiling
**compile tests**
Install gmock and gtest, use the gtest embedded in gmock and don't install libgtest-dev
sudo apt-get install google-mock; cd /usr/src; sudo cmake .; sudo make; sudo mv lib*.a gtest/lib*.a /usr/lib; sudo mv gtest/include/gtest /usr/include/
**install common deps**
Including: git g++ make libssl-dev
**install gflags protobuf leveldb**
Including: libgflags-dev libprotobuf-dev libprotoc-dev protobuf-compiler libleveldb-dev
If you need to statically link leveldb, install libsnappy-dev as well.
**compile**
git clone this repo. cd into the repo and run: sh config_brpc.sh --headers=/usr/include
--libs=/usr/lib
**run example**
cd into example/echo_c++, make, run echo_server and echo_client
**run examples with cpu/heap profilers**
Install libgoogle-perftools-dev and re-run config_brpc.sh before compiling
**compile tests**
Install gmock and gtest, use the gtest embedded in gmock and don't install libgtest-dev
sudo apt-get install google-mock; cd /usr/src; sudo cmake .; sudo make; sudo mv lib*.a gtest/lib*.a
/usr/lib;
sudo mv gtest/include/gtest /usr/include/
Rerun config_brpc.sh and run make in test/
### Baidu-internal
**setup directories**
download deps: third-64/gflags@gflags_2-0-0-100_PD_BL third-64/protobuf@protobuf_2-4-1-1100_PD_BL third-64/leveldb@leveldb_1-0-0-0_PD_BL
**compile**
git clone this repo. cd into the repo and run: sh config_brpc.sh --headers=../../../third-64 --libs=../../../third-64
**run examples with cpu/heap profilers**
download deps: third-64/tcmalloc@tcmalloc_1-7-0-200_PD_BL
Rerun config_brpc.sh
# Supported deps:
GCC: 4.8-7.1
Clang: 3.5-4.0
glibc: 2.12-2.25
**setup directories**
download deps: third-64/gflags@gflags_2-0-0-100_PD_BL third-64/protobuf@protobuf_2-4-1-1100_PD_BL
third-64/leveldb@leveldb_1-0-0-0_PD_BL
**compile**
git clone this repo. cd into the repo and run: sh config_brpc.sh --headers=../../../third-64
--libs=../../../third-64
**run examples with cpu/heap profilers**
download deps: third-64/tcmalloc@tcmalloc_1-7-0-200_PD_BL
Rerun config_brpc.sh
# Supported deps
GCC: 4.8-7.1
Clang: 3.5-4.0
glibc: 2.12-2.25
protobuf: 2.4-3.2
gflags: 2.0-2.21
openssl: 0.97-1.1
tcmalloc: 1.7-2.5
gflags: 2.0-2.21
openssl: 0.97-1.1
tcmalloc: 1.7-2.5
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment