Project: Apache bRPC (Orchestration & Management / Remote Procedure Call)
File: getting_started.md

brpc prefers static linkages of deps, so that they don't have to be installed on every machine running the app. brpc depends on following packages: : Extensively used to define global options. : Serializations of messages, interfaces of services. : Required by to record RPCs for tracing. Install common deps, , , : ```shell sudo apt-get install -y git g++ make libssl-dev libgflags-dev libprotobuf-dev libprotoc-dev protobuf-compiler libleveldb-dev ``` If you need to statically link leveldb: ```shell sudo apt-get install -y libsnappy-dev ``` If you need to enable cpu/heap profilers in examples: ```shell sudo apt-get install -y libgoogle-perftools-dev ``` If you need to run tests, install and compile libgtest-dev (which is not compiled yet): ```shell sudo apt-get install -y cmake libgtest-dev && cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv lib/libgtest* /usr/lib/ && cd - ``` The directory of gtest source code may be changed, try `/usr/src/googletest/googletest` if `/usr/src/gtest` is not there. git clone brpc, cd into the repo and run ```shell $ sh config_brpc.sh --headers=/usr/include --libs=/usr/lib $ make ``` To change compiler to clang, add `--cxx=clang++ --cc=clang`. To not link debugging symbols, add `--nodebugsymbols` and compiled binaries will be much smaller. To use brpc with glog, add `--with-glog`. To enable , install thrift first and add `--with-thrift`. Run example ```shell $ cd example/echo_c++ $ make $ ./echo_server & $ ./echo_client ``` Examples link brpc statically, if you need to link the shared version, `make clean` and `LINK_SO=1 make` Run tests ```shell $ cd test $ make $ sh run_tests.sh ``` ```shell mkdir build && cd build && cmake .. && cmake --build . -j6 ``` With CMake 3.13+, we can also use the following commands to build the project: ```shell cmake -B build && cmake --build build -j6 ``` To help VSCode or Emacs(LSP) to understand code correctly, add `-DCMAKEEXPORTCOMPILECOMMANDS=ON` to generate `compilecommands.json` To change compiler to clang, overwrite environment variable `CC` and `CXX` to `clang` and `clang++` respectively. To not link debugging symbols, remove `build/CMakeCache.txt` and cmake with `-DWITHDEBUGSYMBOLS=OFF` To use brpc with glog, cmake with `-DWITH_GLOG=ON`. To enable , install thrift first and cmake with `-DWITH_THRIFT=ON`. Run example with cmake ```shell $ cd example/echo_c++ $ cmake -B build && cmake --build build -j4 $ ./echo_server & $ ./echo_client ``` Examples link brpc statically, if you need to link the shared version, remove `CMakeCache.txt` and cmake with `-DLINK_SO=ON` Run tests ```shell $ mkdir build && cd build && cmake -DBUILDUNITTESTS=ON .. && make && make test ``` is a package manager that supports all platforms, you can use vcpkg to build brpc with the following step: ```shell $ git clone https://github.com/microsoft/vcpkg.git $ ./bootstrap-vcpkg.bat # for powershell $ ./bootstrap-vcpkg.sh # for bash $ ./vcpkg install brpc ``` CentOS needs to install EPEL generally otherwise many packages are not available by

```shell sudo yum install epel-release ``` Install common deps: ```shell sudo yum install git gcc-c++ make openssl-devel ``` Install , , : ```shell sudo yum install gflags-devel protobuf-devel protobuf-compiler leveldb-devel ``` If you need to enable cpu/heap profilers in examples: ```shell sudo yum install gperftools-devel ``` If you need to run tests, install and compile gtest-devel (which is not compiled yet): ```shell sudo yum install gtest-devel ``` git clone brpc, cd into the repo and run ```shell $ sh config_brpc.sh --headers="/usr/include" --libs="/usr/lib64 /usr/bin" $ make ``` To change compiler to clang, add `--cxx=clang++ --cc=clang`. To not link debugging symbols, add `--nodebugsymbols` and compiled binaries will be much smaller. To use brpc with glog, add `--with-glog`. To enable , install thrift first and add `--with-thrift`. Run example ```shell $ cd example/echo_c++ $ make $ ./echo_server & $ ./echo_client ``` Examples link brpc statically, if you need to link the shared version, `make clean` and `LINK_SO=1 make` Run tests ```shell $ cd test $ make $ sh run_tests.sh ``` Same with brpc builds itself to both static and shared libs by default, so it needs static and shared libs of deps to be built as well. Take as example, which does not build shared lib by default, you need to pass options to `cmake` to change the behavior: ```shell $ cmake . -DBUILDSHAREDLIBS=1 -DBUILDSTATICLIBS=1 $ make ``` Keep on with the gflags example, let `../gflags_dev` be where gflags is cloned. git clone brpc. cd into the repo and run ```shell $ sh configbrpc.sh --headers="../gflagsdev /usr/include" --libs="../gflags_dev /usr/lib64" $ make ``` Here we pass multiple paths to `--headers` and `--libs` to make the script search for multiple places. You can also group all deps and brpc into one directory, then pass the directory to --headers/--libs which actually search all subdirectories recursively and will find necessary files. To change compiler to clang, add `--cxx=clang++ --cc=clang`. To not link debugging symbols, add `--nodebugsymbols` and compiled binaries will be much smaller. To use brpc with glog, add `--with-glog`. To enable , install thrift first and add `--with-thrift`. ```shell $ ls my_dev gflagsdev protobufdev leveldbdev brpcdev $ cd brpc_dev $ sh config_brpc.sh --headers=.. --libs=.. $ make ``` Same with Note: With same environment, the performance of the MacOS version is worse than the Linux version. If your service is performance-critical, do not use MacOS as your production environment. The code at master HEAD already supports M1 series chips. M2 series are not tested yet. Please feel free to report remaining warnings/errors to us by issues. Compile brpc with docker: ```shell $ mkdir -p ~/brpc $ cd ~/brpc $ git clone https://github.com/apache/brpc.git $ cd brpc $ docker build -t brpc:master . $ docker images $ docker run -it brpc:master /bin/bash ``` Install dependencies: ```shell brew install ./homebrew-formula/protobuf.rb brew install openssl git gnu-getopt coreutils gflags leveldb ``` If you need to enable cpu/heap profilers in examples: ```shell brew install gperftools ``` If you need to run tests, googletest is required. Run `brew install googletest` first to see if it works. If not (old homebrew does not have googletest), you can download and compile googletest by your own: ```shell git clone https://github.com/google/googletest -b release-1.10.0 && cd googletest/googletest && mkdir build && cd build && cmake -DCMAKECXXFLAGS="-std=c++11" .. && make ``` After the compilation, copy `include/` and `lib/` into `/usr/local/include` and `/usr/local/lib` respectively to expose gtest to all apps openssl installed in Monterey may not be found at `/usr/local/opt/openssl`, instead it's probably put under `/opt/homebrew/Cellar`. If the compiler cannot find openssl Run `brew link openssl --force` first and check if `/usr/local/opt/openssl` appears. If above command does not work, consider making a soft link using `sudo ln -s /opt/homebrew/Cellar/openssl@3/3.0.3

Note that the installed openssl in above command may be put in different places in different environments, which could be revealed by running `brew info openssl`. git clone brpc, cd into the repo and run ```shell $ sh config_brpc.sh --headers=/usr/local/include --libs=/usr/local/lib --cc=clang --cxx=clang++ $ make ``` The homebrew in Monterey may install software at different directories from before. If path related errors are reported, try setting headers/libs like below: ```shell $ sh config_brpc.sh --headers=/opt/homebrew/include --libs=/opt/homebrew/lib --cc=clang --cxx=clang++ $ make ``` To not link debugging symbols, add `--nodebugsymbols` and compiled binaries will be much smaller. To use brpc with glog, add `--with-glog`. To enable , install thrift first and add `--with-thrift`. Run example ```shell $ cd example/echo_c++ $ make $ ./echo_server & $ ./echo_client ``` Examples link brpc statically, if you need to link the shared version, `make clean` and `LINK_SO=1 make` Run tests ```shell $ cd test $ make $ sh run_tests.sh ``` Same with c++11 is turned on by default to remove dependencies on boost (atomic). The over-aligned issues in GCC7 is suppressed temporarily now. Using other versions of gcc may generate warnings, contact us to fix. Adding `-Dconst=unused` to cxxflags in your makefiles is a must to avoid . no known issues. no known issues. and in ) introduce some proto3 syntax, so currently bRPC is no longer compatible with pb 2.x version. If you want to use pb 2.x version, you can use bRPC version before 1.8.0. Arena in pb 3.x is not supported yet. no known issues. required by https. brpc does not link by default. Users link tcmalloc on-demand. Comparing to ptmalloc embedded in glibc, tcmalloc often improves performance. However different versions of tcmalloc may behave really differently. For example, tcmalloc 2.1 may make multi-threaded examples in brpc perform significantly worse(due to a spinlock in tcmalloc) than the one using tcmalloc 1.7 and 2.5. Even different minor versions may differ. When you program behave unexpectedly, remove tcmalloc or try another version. Code compiled with gcc 4.8.2 and linked to a tcmalloc compiled with earlier GCC may crash or deadlock before main(), E.g: When you meet the issue, compile tcmalloc with the same GCC. Another common issue with tcmalloc is that it does not return memory to system as early as ptmalloc. So when there's an invalid memory access, the program may not crash directly, instead it crashes at a unrelated place, or even not crash. When you program has weird memory issues, try removing tcmalloc. If you want to use or , do link `libtcmallocandprofiler.a`. These two profilers are based on tcmalloc. does not require tcmalloc. When you remove tcmalloc, not only remove the linkage with tcmalloc but also the macro `-DBRPCENABLECPU_PROFILER`. brpc implements a default which conflicts with glog. To replace this with glog, add --with-glog to configbrpc.sh or add `-DWITHGLOG=ON` to cmake. brpc detects valgrind automatically (and registers stacks of bthread). Older valgrind(say 3.2) is not supported. no known issues. We provide a program to help you to track and monitor all brpc instances. Just run somewhere and launch need-to-be-tracked instances with -trackmeserver=SERVER. The trackmeserver will receive pings from instances periodically and print logs when it does. You can aggregate instance addresses from the log and call builtin services of the instances for further information.