This version of dco/c++ is suitable for Visual Studio versions between VS2010 and VS2013.
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 (VS2010 <= VS version <= VS2013)
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.
|- doc -|- in.html (Installer's Note - this document) | |- userguide.pdf (User Guide as pdf) | |- licence -|- * (licence management documentation) | |- batch -|- envvars.bat (batch file to set environment | variables for the C++ compiler) | |- bin -|- (licence management tools, and compiler run-time DLLs) dcw6i33nal -| | |- include -|- *.hpp (C++ header files) | |- examples -|- (directories containing various example programs | | from the dco/c++ user guide, along with Makefiles) | |- case_studies -|- (more sophisticated examples from the dco/c++ | | user guide) | |- lib -| (dco libraries and compiler run-time libraries)
By default, the dco/c++ materials are installed in
C:\Program Files\NAG\DC33\dcw6i33nalor 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 DOS command window by executing the file dcw6i33nal\batch\envvars.bat.
This software is provided with an uninstallation facility via the Windows Control Panel.
dcw6i33nal_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 and the environment variables will be modified. The default installation location may be 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 by running the
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:
DCW6I33NA TRIAL 2018/03/31 "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 DCW6I33NA licence.datOtherwise the key can be installed for the current user,
klreg /current_user DCW6I33NA licence.dat
The environment variable may be set from the Control Panel.
More sophisticated examples (case studies) are located in folders
If it is planned to use Microsoft Visual Studio to build programs that use dco/c++, each user should set the appropriate options.
Start Visual Studio and create your project in the usual way. We assume that your project is going to make use of the dco/c++.
The library is intended to be run in fully optimized mode, so for best perfomance you should set the active configuration to Release. Once Visual Studio has been opened, you can do this from the Toolbar or alternatively via the Build|Configuration Manager menus. Note that if you work in Debug mode you should use dco/c++ libraries linked against debug version of C/C++ run-times (libdcoc_M*d) see the table below for details.
Make sure the Platform is set to x64 (to ensure compatibility with this 64-bit implementation of dco/c++). This can be changed via the Configuration Manager... button on the Property Pages.
The following steps show how to add dco/c++ to the project:
The folders are located at;
Include Directories install_dir\include Library Directories install_dir\libThe default install_dir can be found in Section 4.1.
Click on the Apply button to accept the changes.
Click on the OK button to accept the changes and close the form.
Open the Property Pages again (as detailed above) and click/expand Configuration Properties (if required) and then C/C++, then click on Code Generation in the left hand panel. Then, from the right hand panel, select Runtime Library and change this to the appropriate version, for example /MD or /MT. This must match the version of the dco/c++ that you link to.
Click on the OK button to accept the changes and close the form.
|dco/c++ Library||C/C++ Run-time Libraries|
|libdcoc_MD.lib||Multi-threaded DLL (/MD) (Release)|
|libdcoc_MT.lib||Multi-threaded (/MT) (Release)|
|libdcoc_MDd.lib||Multi-threaded DLL (/MDd) (Debug)|
|libdcoc_MTd.lib||Multi-threaded (/MTd) (Debug)|
The project should now compile and link using the appropriate choice from the Build menu.
To run a program from within the Microsoft Development Environment, the program may be executed via the Debug menu (by selecting Start Without Debugging (Ctrl+F5), for example). If you are using /MD form of the library, you need to ensure that DLLs located in install_dir\bin folder are accessible at run time; therefore the PATH environment variable must contain install_dir\bin folder.
If a data file needs to be attached to the standard input or the output of a program needs to be redirected to the standard output, this can be achieved by selecting the Debugging section on the Properties form and inserting the appropriate commands in the Command Arguments field, e.g.
< input_file > output_file
If the input and output files are not in the application's working directory, full or relative paths may need to be specified. This directory may be set via the Working Directory field, which is also on the Debugging page of the Properties form.
for information about the NAG Technical Support Service, including details of the NAG Technical Support Service contact points. We would also be delighted to receive your feedback on NAG's products and services.
for worldwide contact details for the Numerical Algorithms Group.