Skip to content

Build 'ArborGVT'

Ruslan Garipov edited this page Apr 21, 2016 · 1 revision

Build 'ArborGVT'

C++

To build ArborGVT binaries you need:

  • Microsoft Visual Studio 2015 Update 2,
  • Intel Parallel Studio 2016 Update 2 (if you plan to get releases built by ICL),
  • Standalone Windows Software Development Kit (SDK) for Windows 10 (you must install standalone Windows 10 SDK if you plan to debug the source code; this is requirement of Direct3D -- you must have D3D SDK (which is part of Windows 10 SDK) to be able to debug DirectX code),
  • MINGW shell (to be able to run GNU make on Windows platform).

If you installed Microsoft Visual Studio, Intel Parallel Studio and/or Windows SDK into non-default location you must correct toolset paths in the following files: 'icc.mk', 'msvc.mk', 'winsdk.mk'. If you do not plan to build release by Intel C++ you have to edit Makefile (remove lines that refer to ICC/ICL).

Once you've got all above just do this:

$ cd /...path-to-ArborGVT-source-code.../cpp/solution/Makefile/gnumake
make

If make succeeded you get release build (by default) made by MSVC and ICL for x86-64 and x86 platforms (located at '/...path-to-ArborGVT-source-code.../cpp/build'). If you make default target or set project variable to dtsample value you will get binaries for both 'ArborGVT' library and 'dtsample' application. To build only 'ArborGVT' library set project variable to arborgvt:

$ make project=arborgvt

To gain additional control over build use dedicated makefiles:

$ make toolchain=icc platform=x86-64 releasetype=release --file=arborgvt.mk

For both arborgvt.mk and dtsample.mk files one can use the following variables to manage build process:

  • toolchain: toolset to use. Possible values are icc (Intel C++) and msvc (Microsoft VC++).
  • platform: target platform. Possible values are x86-64 and x86.
  • releasetype: result build. Possible values are release and debug.
Clone this wiki locally