CIMPL Installation, Configuring Visual Studio 2003 and adding support for CIMPL

• The following assumes that you already created a working Visual Studio 2003 project and you want to add support for CIMPL. If you are not sure how to create a new project, a sample VS.Net 2003 project for a console application is provided here.
• Unzip the CIMPL package. You will see a directory for ImageMagick installer. "include" directory that has the header files, templates and the full source code for CIMPL 1.0. "dlls" directory contains supplementary DLLs, and "libs" directory includes the static library files.
• CIMPL package comes with ImageMagick bundled. ImageMagick is needed to read/write any kind of image formats. Double click on the installation file for ImageMagick, then follow the instructions on screen. You can safely keep the defaults during installation.
• Copy the DLL's to the C:\Windows\System32\ (or equivalent) folder. Alternatively you can keep these DLL's at the same directory as the executable you create, or copy these DLL's to a folder and add this folder to the system PATH.
• Add the include directory to the include path of your Visual Studio 2003 project. To do this, right click on the project name and select "properties". Choose "All configurations", select C/C++ -> General. Then add the include directory. See the following image:
  
• There are both debug and release versions of the static libraries included. Debug versions end with _debug.lib. Add this library folder to your project. See the following image:
  
• Add the *.lib files to your project. Debug versions of the libraries (*_debug.lib) needs to be added to the Debug configuration, and the rest to the Release configuration. See the following image:
  

• Add
  
  #include "cimpl.h"
  using namespace CIMPL;

  #include "cimpltoolboxes.h"
  using namespace Lapack;
  using namespace Blas;
  using namespace IO;
  using namespace MathCore;
  using namespace Analysis;

  to your code to start using CIMPL.

Compiling in Release mode is strongly suggested if your code results in computationally expensive operations. Release mode compared to the Debug mode may speed up the run-time upto 10 times.