milvus/cpp
xj.lin d7c7720ef6 update cmakefile
Former-commit-id: 2827b60ab09f52a244a6da690c42340884a48f39
2019-04-19 16:43:30 +08:00
..
cmake Add cpp source code 2019-04-12 20:58:45 +08:00
conf client call api 2019-04-18 10:50:24 +08:00
src feat(db): cleanup pre db destruction 2019-04-19 16:08:12 +08:00
test_client refine code 2019-04-18 17:26:03 +08:00
unittest update cmakefile 2019-04-19 16:43:30 +08:00
build.sh add readme 2019-04-14 20:21:07 +08:00
CMakeLists.txt add TopK 2019-04-19 16:07:45 +08:00
LICENSE.txt Add LICENSE.txt and RELEASE.md 2019-04-14 20:12:34 +08:00
README.md refine code 2019-04-18 17:26:03 +08:00
RELEASE.md Add LICENSE.txt and RELEASE.md 2019-04-14 20:12:34 +08:00
start_server.sh refine code 2019-04-18 17:26:03 +08:00
stop_server.sh refine code 2019-04-18 17:26:03 +08:00

Compilation

Step 1: install necessery tools

centos7 : yum install gfortran
ubuntu16.04 : sudo apt-install install gfortran libsqlite3-dev

Step 2: build third-parties

Note: If you want to debug into third-parties, you can build debug with CXXFLAGS='-g -O0' with option
-t Debug

cd [sourcecode path]/cpp/thid_party ./build.sh -t Debug ./build.sh -t Release

Step 3: build(output to cmake_build folder)

cmake_build/src/vecwise_server is the server

cmake_build/src/libvecwise_engine.a is the static library

cd [sourcecode path]/cpp
./build.sh -t Debug
./build.sh -t Release

To build unittest:

./build.sh -u
or
./build.sh --unittest

Luanch server

Set config in cpp/conf/server_config.yaml

Then luanch server with config:

cd [build output path]
start_server.sh
stop_server.sh

Luanch test_client(only for debug)

If you want to test remote api, you can build test_client. test_client use same config file with server:

cd [build output path]/test_client
test_client -c [sourcecode path]/cpp/conf/server_config.yaml