This document provides implementation-specific information relating to the installation of dco/c++ gold.
This version of dco/c++ is suitable for Visual Studio versions VS2019 and newer.
This implementation is considered suitable for operation on the computer systems detailed below:
hardware: Intel 64 systems and compatible (including AMD64) operating system: Microsoft Windows 64-bit editions C++ compiler: Microsoft 64-bit C/C++ compiler (VS version >= VS2019)
Please check the following URL:
for details of any new information related to the applicability or usage of this implementation. Details of any other systems on which it has been tested may also be found on this page.
|- batch -|- envvars.bat (setting the environment variables)    |    |- bin -|- (licence management tools, and compiler run-time DLLs)    |    |- case_studies -|- (more sophisticated examples from the    | | user guide, along with the corresponding CMakeLists.txt)    |    |- cmake -|- (auxiliary files required for building and testing with CMake)    |    |- doc -|- in.html (Installer's Note - this document)    | |- userguide.pdf (User Guide as pdf)    | |- licence -|- * (licence management documentation) dgw6i04xnl_v420 -|    |    |- examples -|- (directories containing various example programs    | | from the user guide, along with the CMakeLists.txt)    |    |- include -|- *.hpp (C++ header files)    |    |- lib -|- (libraries and compiler run-time libraries)    |    |- CMakeLists.txt -|- (used for building and testing)
By default, the dco/c++ materials are installed in
C:\Program Files\NAG\DC42\dgw6i04xnl_v420or the equivalent for your locale.
The environment variables PATH, LIB and INCLUDE are used by the Microsoft C++ compiler to locate run-time and compile-time directories used by dco/c++.
These environment variables can be updated during installation of dco/c++ with permission of the installer. Alternatively, you may set the variables on a temporary basis in a Visual Studio Command Prompt by executing the file dgw6i04xnl_v420\batch\envvars.bat. Note that CMake picks up the right paths automatically when find_package(NAG_dco_cpp) is used.
This software is provided with an uninstallation facility via the Windows Control Panel.
dgw6i04xnl_v420_setup.exe /verysilentfrom a command prompt. With the first version, the user sees a progress bar on the screen as the installation occurs, whereas with the second, nothing is displayed. The files will be installed to the default location, unless the default installation location gets overridden by using the /dir switch, e.g.
In order to enable the software, NAG will issue you with a licence key. The licence key is contained in a text file consisting of details of the software that will be enabled. For evaluation purposes a trial licence may be used. Before obtaining a full licence you need to know the Kusari hostid of the system on which you intend to use this product. How to do this is described below.
The easiest way to request a licence key is to use the Kusari Installer GUI described in the next section. Once you have a key, the same GUI can be used to install it.
The information below covers the most common requirements. For more
complex licensing situations, please see the Kusari documentation
To request a licence key, run the Kusari Installer program, which may
be accessed via the Start Menu or
Click on the
The NAG support team will send you the Kusari licence key by email.
A short term (demonstration or trial) licence key contains one or more lines like the following:
DGW6I04XN TRIAL <EXPIRY_DATE> "EMnxidA3oeoj0F1Yvi5ibxPjB7"Specifically, it has a line containing the word TRIAL. Longer term licence keys must be locked to a specific computer, i.e. they will enable the software on one computer only. These licence keys typically include the word NODE or FULL instead of the word TRIAL above and may contain extra fields.
Once you have obtained one of the above licence keys, the Kusari
Installer program may be used to install the key in the Windows
Registry. Paste the key into the edit box on the main Kusari
Installer dialog and then click on the
The khostid command may be found in the
klreg DGW6I04XN licence.datOtherwise the key can be installed for the current user,
klreg /current_user DGW6I04XN licence.dat
The environment variable may be set from the Control Panel.
More sophisticated examples (case studies) are located in folders
cmake -S "<path-to-source>" -G "< A Makefiles Generator >"to generate the build system with the Makefiles generator of your choice. Then execute the corresponding build command to build all the available examples and case studies.
You can use
NMAKE as follows:
cmake -S "C:\Program Files\NAG\DC42\dgw6i04xnl_v420" -G "NMake Makefiles" nmake
ctestNote that there may be small differences between observed and reference results, depending on the environment.
ga1sexample, use the following:
nmake examples.ga1s examples\examples.ga1s.exe
cmake -S "C:\Program Files\NAG\DC42\dgw6i04xnl_v420" -G "Visual Studio 15 2017"will create
dco_cpp.slnin the current directory. See here for a list of available generators.
dco_cpp.sln can be opened with Visual Studio 2017
to load the solution. Each example and each case study has its own
project and can be built and run individually. Additionally, the
project "ALL_BUILD" can be used to build all examples and case
studies at once. Then, building the "RUN_TESTS" project will execute all examples
and case studies. Please note that "ALL_BUILD" can not be used to
run the executables.