This page began as the Few-Frills How-To for building on Windows 10, but now we are trying to fill it in with more details. Please help give us feedback on what needs to be improved.
- Development Tools
- Build/Install Libraries
- Build OpenSpace
The source code for OpenSpace is distributed via GitHub, and so you will need a Git client to obtain a copy of the source code. OpenSpace uses git submodules, so a client which can handle these gracefully is preferred. These include:
- Git GUI (a part of the basic git download or Visual Studio)
Visual Studio 2019 is the standard Interactive Development Environment (IDE) for Windows. The “community” version is a free download. When you install it, be sure to select “Custom” configuration and select the C++ compiler – it is not included by default. You can also select a git client here (“Git GUI”). Installation could take a while (like an hour or so, depending on the machine). We are following the development of the C++ language quite closely, so there are more and more features that are no longer supported in Visual Studio 2017
- Download and run the CMake installer
- If you are upgrading from version 3.4 or earlier, uninstall first. We require CMake 3.12 or newer.
Building OpenSpace will be easier if you follow a few guidelines about where you put the source code and where you build OpenSpace the the libraries it needs. OpenSpace depends on several other software components, which are loaded as git submodules when you do a recursive clone. These are all in the
ext/ subdirectory. One of these is a library called Ghoul, and Ghoul has it’s own submodules, in
Checkout OpenSpace recursively using SourceTree, SmartGit, or the command line. The command line git command is:
git clone --recursive https://github.com/OpenSpace/OpenSpace
- Open CMake and set “Where is the source code:” to the directory you just cloned from github, for example
- Set “Where to build the binaries:” to the build subdirectory, for example:
- Set CMake variables to enable or disable specific modules. The default settings are fine, but make sure that the following are enabled:
- Press the
Configurebutton in CMake. Expect errors, which you will then correct:
- The first time you press
Configureyou are asked to select a “generator” for the project. Select “Visual Studio 15 2017 Win64” (the Win64 is the important part)
- Configure again, as needed, until you resolve all the errors (except anything that says “this warning is for project developers”)
- You can start over by pulling down “File->Delete Cache”.
- The first time you press
- Press the
Generatebutton. This creates the Visual Studio Solution (
.sln) file and supporting Project (
- The generated solution file can be opened via
Open Project. Otherwise, navigate to the build directory and open the main Solution file, called
- Select either the “Launcher” or the “OpenSpace” project as a startup project via right click in the “Solution Explorer” and build them
- You can start either application from within Visual Studio or by navigating to OpenSpace/bin/openspace
- Create your build directory to store the configuration files anywhere outside the source files. It’s not required to be named
buildbut that’s common. You can keep it in the top level of your repository.
- Unlike the Mac & Linux platforms, the Windows Debug version will run much slower than its Release counterpart due to additional tests by the standard library. The
RelWithDebInfobuild option will enable optimizations but also makes debugging inside of Visual Studio possible.
- When in doubt File -> Delete Cache and start again.
- To execute cmake from visual studio command line, cmake args must be passed with -D
cd develop/OpenSpace mkdir build & pushd build cmake -DCMAKE_BUILD_TYPE=Release -G "Visual Studio 15 2017 Win64" .. popd cmake --build build --config Release
- You might find it easier to use SSH instead of HTTPS, especially if you’re using Two-Factor Authentication with GitHub.
- If you use the command line interface for
git, remember that OpenSpace has many submodules. You’ll want to
git clone --recursiveand/or use the
git submodulecommands. The
submodulecommands will need to be run in both the main repository and
- When switching between
Debugconfiguration in Visual Studio, there has been cases where some targets aren’t getting rebuilt properly. Therefore, highlight
VRPNin the solution, right click and select
Rebuild Selectionafter changing build configuration.
If Windows is complaining that it cannot find the
VCOMP120.dll, download https://www.microsoft.com/en-us/download/details.aspx?id=40784 the Visual Studio 2013 Redistributable. On Windows 10, this is not installed by default anymore.