I was not able to find a place that specifically address the build process on Windows, so here are my quick notes.
These are from the perspective of a non-C++ developper, so some of these may seem obvious for seasoned C++ devs
I’m using Visual Studio 2017 (15.7) on Win10.
- Need to install Boost
- download the 1.52.0 .7z or .zip archive from https://sourceforge.net/projects/boost/files/boost/1.52.0/
- unzip it and copy it in
C:\Program Files\boost_1_52_0\. Please note that the Boost documentation says to copy them to
C:\Program Files\boost\boost_1_52_0\but the .vcxproj in fdb ommit the “\boost” middle folder !
- if you still get errors about boost includes, double check the path is correct! Also you need Boost v1.52, not 1.55 or later !
- Need to install Python 2.7
- Download the Windows x86-64 MSI installed for Python 2.7.x for Windows
- It must be installed to the default location of
- Need to install WiX ToolSet for the MSIInstaller project
- if you don’t care about building the MSI installer, just unload the project from the solution explorer.
- if VS does not want to open the project, you may need to reinstall WiX
- download latest from http://wixtoolset.org/releases/
- you may also need to install the “Wix Toolset Visual Studio 2017 Extension” (or 2015) if you get warning about project type not supported.
- Need to install Java JDK 8
- If you don’t care about building the java binding, just unload the project from the solution explorer.
- note: You may need to sell your soul to Oracle to accept the agreement, which I was not willing to do.
- For syntax highlighting:
- To have syntax highlighting of the flow keywords, you need to copy the
usertype.datfile located in
flow/actorcompiler/in your Visual Studio installation dir, following the instructions at https://msdn.microsoft.com/en-us/library/zy61y8b8.aspx
- ReSharper C++ does not understand the flow/actor syntax by default (as of version 2018.1) so you may need to disable Resharper when working on the code.
First build (in Debug) can be slow (several minutes on a fast machine). Next builds should be faster.
Build output is in the bin\Debug or bin\Release folder.
Quick sanity check: start the
fdbcli.exe in the build output folder. If you get
"WARNING: One or more of the processes in the cluster is incompatible with this version of fdbcli." this is still a success, it just means that it is connected to your existing installed cluster which is probably a lower version.