Skip to content

Instantly share code, notes, and snippets.

@rcx
Created November 18, 2017 01:36
Show Gist options
  • Save rcx/8abf465f208740f22b21636fa3b9e855 to your computer and use it in GitHub Desktop.
Save rcx/8abf465f208740f22b21636fa3b9e855 to your computer and use it in GitHub Desktop.
Compiling Veles on Windows

Note: change cmake -G parameter to whatever visual studio you need... just pass cmake -G "" to make it list all the options

git clone https://github.com/codilime/veles
cd veles

Open CMakeLists.txt add this at the top:

set(CMAKE_PREFIX_PATH "C:\\Path\\To\\Qt\\qt-5.6.0-x64-msvc2015\\5.6\\msvc2015_64")
set(OPENSSL_DLL_DIR "C:\\Path\\To\\veles\\openssl")
set(ZLIB_LIBRARY "C:\\Path\\To\\veles\\zlib\\lib\\zlib.lib")
set(ZLIB_INCLUDE_DIR "C:\\Path\\To\\veles\\zlib\\include")

Okay now:

mkdir zlib
mkdir zlib/lib
mkdir zlib/include
mkdir openssl

Copy ssleay32.dll and libeay32.dll into openssl/ , you can find these in a prebuilt version of Veles Dont worry if it says 32, these are actually 64-bit if you grab it from a prebuilt Veles

Now we need to build zlib Get zlib: https://zlib.net/ , get the source code in the zlib folder:

mkdir build
cd build
cmake -G "Visual Studio 14 2015 Win64" ..

Then open zlib.sln in visual studio, change configuration from Debug to RelWithDebInfo Copy zlib.lib into veles/zlib/lib Copy zlib.h and zconf.h into veles/zlib/include We will grab zlib.dll later

Make sure you have python3 installed, and that py is in your path and points to python3 (VERY IMPORTANT)

Now back in veles

mkdir build
cd build
cmake -G "Visual Studio 14 2015 Win64" -D CMAKE_BUILD_TYPE=Release ..

It should whine about gmock and gtest, ignore it, as long as it finds everything else.

OK now open VELES.sln

Build it, this will take a while.

Results in Veles UI, but we need to add some support files or we cant run it yet. Copy veles-server from your Veles installation to same folder as "Veles UI" output folder (build) Now copy the zlib.dll we built earlier into Veles UI output folder

You can now run it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment