5656
5757By default, ` make ` command downloads gRPC source code from github and compile it under the CMake build directory.
5858
59- You can use a pre-built gRPC lib build by youself . milvus-sdk-cpp 2.4 is using gRPC v1.59.0, make sure your gRPC version is compatible.
59+ You can use a pre-built gRPC lib build by yourself . milvus-sdk-cpp 2.4 is using gRPC v1.59.0, make sure your gRPC version is compatible.
6060
6161### Download gRPC source code
6262``` shell
@@ -80,7 +80,7 @@ $ cmake -DCMAKE_INSTALL_PREFIX=/path/to/pre-installed/grpc -DBUILD_SHARED_LIBS=
8080$ make
8181$ make install
8282```
83- Make sure the ` BUILD_SHARED_LIBS ` is ` ON ` since milvus-sdk-cpp dynamiclly links to gRPC.
83+ Make sure the ` BUILD_SHARED_LIBS ` is ` ON ` since milvus-sdk-cpp dynamically links to gRPC.
8484
8585### Use ` GRPC_PATH ` to specify the external gRPC and build milvus-sdk-cpp
8686``` shell
@@ -113,7 +113,7 @@ to automatic format all c++ source code
113113## Run tests, and add testing code
114114Milvus C++ SDK using googletest as a test framework. You could run ` make test ` to run unit testing and integration testing.
115115
116- If you have an pre-installed gRPC, use ` GRPC_PATH ` to specify the path:
116+ If you have a pre-installed gRPC, use ` GRPC_PATH ` to specify the path:
117117``` shell
118118$ make test GRPC_PATH=/path/to/pre-installed/grpc
119119```
@@ -132,8 +132,8 @@ $ ./cmake_build/test/testing-st
132132```
133133
134134### Run acceptance/system tests with real Milvus server
135- The acceptance/system tests are not included by default. You cloud using the below commands to run them:
136- - ` make st ` user the top source directory
135+ The acceptance/system tests are not included by default. You could use the below commands to run them:
136+ - ` make st ` under the top source directory
137137- ` make system-test ` under the CMake build directory
138138
139139The acceptance/system tests will startup container by docker, and using jq to capture the output from docker inspect,
@@ -154,7 +154,7 @@ After the command, a folder named "code_coverage" will be created under the proj
154154You could open the ** code_coverage/index.html** by a web browser to review the code coverage report.
155155
156156## Generate documentation
157- Milvus C++ SDK using ** doxygen** tool to generate documentation. Run ` make documentation ` to generate documentation.
157+ Milvus C++ SDK uses ** doxygen** tool to generate documentation. Run ` make documentation ` to generate documentation.
158158Typically, we only publish documentation before releasing a new sdk version.
159159Since the ** doxygen** is not included in the ` install_deps.sh ` , you need to manually install it if you want to generate the documentation by yourself.
160160
@@ -165,7 +165,7 @@ Since the **doxygen** is not included in the `install_deps.sh`, you need to manu
165165The setup steps and development environment for macOS are similar to Linux.
166166You could use ` install_deps.sh ` to install dependencies and use the same ` make ` commands for build, lint, test, and coverage.
167167
168- ### Prerequests
168+ ### Prerequisites
169169Before you run ` install_deps.sh ` to install dependencies, you should make sure:
170- - Already installed (Homebrew) [ https://brew.sh/ ]
171- - Install Command line tools for Xcode, by command: ` xcode-select --instal `
170+ - Already installed [ Homebrew ] ( https://brew.sh/ )
171+ - Install Command line tools for Xcode, by command: ` xcode-select --install `
0 commit comments