Lines Matching +full:libc +full:- +full:ares +full:- +full:dev

1 gRPC C++ - Building from source
5 …/cpp#to-start-using-grpc-c) instructions for guidance on how to add gRPC as a dependency to a C++ …
7 # Pre-requisites
12  $ [sudo] apt-get install build-essential autoconf libtool pkg-config
17  $ [sudo] apt-get install cmake
23  $ [sudo] apt-get install clang libc++-dev
34  $ [sudo] xcode-select --install
58 - Install Visual Studio 2019 or later (Visual C++ compiler will be used).
59 - Install [Git](https://git-scm.com/).
60 - Install [CMake](https://cmake.org/download/).
61 - Install [nasm](https://www.nasm.us/) and add it to `PATH` (`choco install nasm`) - *required by b…
62 - (Optional) Install [Ninja](https://ninja-build.org/) (`choco install ninja`)
67 for gRPC's dependencies (that's done by the `submodule` command or `--recursive` flag). Use followi…
73  $ git clone -b RELEASE_TAG_HERE https://github.com/grpc/grpc
75  $ git submodule update --init
81 > git clone -b RELEASE_TAG_HERE https://github.com/grpc/grpc
83 > git submodule update --init
112 $ bazel test --config=dbg //test/...
116 This is because gRPC isn't fully compatible with bzlmod yet. To do this, add --enable_bzlmod=false …
125 Run from the grpc directory after cloning the repo with --recursive or updating submodules.
127 $ mkdir -p cmake/build
133 If you want to build shared libraries (`.so` files), run `cmake` with `-DBUILD_SHARED_LIBS=ON`.
143 > @rem Run from grpc directory after cloning the repo with --recursive or updating submodules.
146 > cmake .. -G "Visual Studio 16 2019"
147 > cmake --build . --config Release
150 Using gRPC C++ as a DLL is not recommended, but you can still enable it by running `cmake` with `-D…
157 > @rem Run from grpc directory after cloning the repo with --recursive or updating submodules.
162 > cmake ..\.. -GNinja -DCMAKE_BUILD_TYPE=Release
163 > cmake --build .
166 Using gRPC C++ as a DLL is not recommended, but you can still enable it by running `cmake` with `-D…
172 That said, we don't actively prohibit building DLLs on windows (it can be enabled in cmake with `-D…
174 - you've been warned that there are some important drawbacks and some things might not work at all …
175 - we don't have extensive testing for DLL builds in place (to avoid maintenance costs, increased te…
186 * module - build dependencies alongside gRPC. The source code is obtained from
188 * package - use external copies of dependencies that are already available
190 you pre-installed them using CMake with the `CMAKE_INSTALL_PREFIX` option.
193 c-ares before building gRPC. On the other hand, if you set
194 `gRPC_CARES_PROVIDER=package`, then CMake will search for a copy of c-ares
200 * Set `-DgRPC_INSTALL=ON`
218 $ cmake ../.. -DgRPC_INSTALL=ON                \
219               -DCMAKE_BUILD_TYPE=Release       \
220               -DgRPC_ABSL_PROVIDER=package     \
221               -DgRPC_CARES_PROVIDER=package    \
222               -DgRPC_PROTOBUF_PROVIDER=package \
223               -DgRPC_RE2_PROVIDER=package      \
224               -DgRPC_SSL_PROVIDER=package      \
225               -DgRPC_ZLIB_PROVIDER=package
230 ### Cross-compiling
232 You can use CMake to cross-compile gRPC for another architecture. In order to
238 targeting for your cross-compile. Once you have done so, you can write a
245 $ cmake ../.. -DCMAKE_TOOLCHAIN_FILE=path/to/file
249 [Cross-compile example](test/distrib/cpp/run_distrib_test_cmake_aarch64_cross.sh)
266 … error on linux such as 'aclocal-1.15: command not found', which can happen if you ran 'make' befo…
268 $ git clean -f -d -x && git submodule foreach --recursive git clean -f -d -x
269 $ [sudo] apt-get install build-essential autoconf libtool pkg-config