For Linux platforms, the debug and release versions need to be built separately, using two different
 build directories. Command
 
	cmake <relative path from debug build directory to the src-directory> -DCMAKE_BUILD_TYPE=Debug
 
            
 will create the makefiles for a debug version of the code. Command 
 
	cmake <relative path from release build directory to the src-directory> -DCMAKE_BUILD_TYPE=Release
	
 will create the makefiles for a release version of the code. There is an example
 shell script build-for-linux.sh in the top-level directory which creates a directory
 Release.Linux and invokes cmake from this new directory, using the Release option.
 You can copy and modify this script for your preferred build options.
 
 
 For building the graphical user interface as well, the above mentioned commands have to be changed to:
	
	cmake -Dgui=ON <relative path from debug build directory to the src-directory> -DCMAKE_PREFIX_PATH=<absolute path to Qt>/Qt/5.7/gcc_64/ -DCMAKE_BUILD_TYPE=Debug
	
for debug mode, respectively
	
	cmake -Dgui=ON <relative path from release build directory to the src-directory> -DCMAKE_PREFIX_PATH=<absolute path to Qt>/Qt/5.7/gcc_64/ -DCMAKE_BUILD_TYPE=Release
	
for release mode. 

 For Mac OSX platforms, the debug and release versions need to be built separately, using two different
 build directories (just as for Linux). Command
 
    cmake <relative path from debug build directory to the src-directory> -DCMAKE_BUILD_TYPE=Debug
    
 will create the makefiles for a debug version of the code. There is an example
 shell script build-for-osx.sh in the top-level directory which creates a directory
 Debug.OSX and invokes cmake from this new directory, using the Debug option.
 You can copy and modify this script for your preferred build options. Also, 
 shell script build-for-xcode.sh creates a directory xcode and invokes cmake there
 to set up an Xcode project for building the library.

 Command
 
    cmake <relative path from release build directory to the src-directory> -DCMAKE_BUILD_TYPE=Release
    
 will create the makefiles for a release version of the code.
 
 For building the graphical user interface use the following commands instead:
 
    cmake -Dgui=ON <relative path from debug build directory to the src-directory> -DCMAKE_PREFIX_PATH=<absolute path to Qt>/Qt/5.7/clang_64/ -DCMAKE_BUILD_TYPE=Debug
 
 for debug mode, respectively
 
	cmake -Dgui=ON <relative path from release build directory to the src-directory> -DCMAKE_PREFIX_PATH=<absolute path to Qt>/Qt/5.7/clang_64/ -DCMAKE_BUILD_TYPE=Release
 
 for release mode.

 For Windows platforms, the debug and release versions will be built at the same time. Please note that you will have to add Qt's dll to your PATH in order to build the gui.
 
 Launch Cmake GUI.
 
 Specify the source code directory and the binaries directory.
 
 For building the graphical user interface the following steps are necessary:
 
 Enable the option `gui`
 
 Click Add Entry.
 
 Write this line for the Name. Command
 
	CMAKE_PREFIX_PATH
	
 Select PATH for the Type. For the value, put the absolute path to. Command
 
	Qt/5.7/msvc2015_64
 
 Click Generate and verify if cmake is using the right compiler.
 
 Click Finish.
 
 will create all the files needed by MSVC. You can now open the project with the .sln file.

 Several properties need to be specified for the MSVC compiler before the library can be built
 without errors. These options can be set by selecting all sub-projects fsm-example, fsm-fsm,
 fsm-generator,...,fsm-trees end entering the properties dialog via context menu (right click).
 There, select C/C++, Command Line and insert in the Additional Options field the following
 command line options for invoking the compiler

      /Za /Dstrdup=_strdup 

 Option /Za enables the use of logical operators not, and, or instead of !, &&, ||,
 but disables the use of function name strdup instead of _strdup. Since the unix worlds
 use strdup, the define /Dstrdup=_strdup lets MSVC see _strdup as required.

 If you do not like this work around, you need to insert the extra include directive

        #include <ciso646>

 in all cpp-files. This defines the not, and, or operators. We do not like this solution,
 so the compiler options are the preferred solution.

 Furthermore, select C/C++, Preprocessor in the properties dialogue and add the 
 preprocessor definitions _CRT_SECURE_NO_WARNINGS and _CRT_NONSTDC_NO_DEPRECATE.
 This suppresses warnings about using fopen(), fgets(), and about using function names
 that MSVC claims to be deprecated but which are syill used in the unix world.