xj.lin 876f6a4c66 1 Support Cpu-version
2 Update build.sh support both cpu-build and gpu-build


Former-commit-id: 3c0ddd7fb2f93ab45b6f9878b71b6541617f92c4
2019-05-11 11:27:06 +08:00
..
2019-04-12 20:58:45 +08:00
2019-04-28 14:48:05 +08:00
2019-05-11 11:27:06 +08:00
2019-05-10 14:32:43 +08:00
2019-05-11 11:27:06 +08:00
2019-05-11 11:27:06 +08:00
2019-05-11 11:27:06 +08:00
2019-04-14 20:12:34 +08:00
2019-05-07 10:10:20 +08:00
2019-04-14 20:12:34 +08:00
2019-04-18 17:26:03 +08:00
2019-04-18 17:26:03 +08:00

Compilation

Step 1: install necessery tools

centos7 : 
    yum install gfortran libsqlite3-dev libsnappy-dev libzstd-dev bzip2
    
ubuntu16.04 : 
    sudo apt-get install gfortran libsqlite3-dev libsnappy-dev libzstd-dev bzip2 liblz4-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