It is assumed any third party tool is properly installed on the host machine.

It is important to understand integration is done at two different levels:

1 - RTOS integration
The generated code is based on C macros that are defined in the "Code template directory". These macro definition call the RTOS system primitives. Currently there are a directories for:
* VxWorks,
* Win32,
* Posix,
* CMX,
* uITRON,
* OSE,
* ThreadX

2 - Debugger integration
To be able to trace execution, set breakpoints, and view variables Real Time Developer Studio Simulator is interfaced with a debugging environment. Depending on the debugger functionnalities there might be differences in the Simulator. Available debugger integrations are:
* Tornado,
* Tasking Cross View Pro debugger,
* gdb (Gnu debugger).
* XRAY

3 - Generation profiles provided in the examples
* Tornado_Windows: Tornado profile for Windows.
* Tornado_Solaris: Tornado profile for Solaris.
* XRAY_OSE_Win: OSE integration to debug with XRAY on Windows.
* OSE_sfk_Win: OSE soft kernel on Windows. No debugger.
* OSE_sfk_Sol: OSE soft kernel on Solaris. No Debugger.
* OSE_Arm_Win: OSE integration on ARM for Windows.
* OSE_Arm_Sol: OSE integration on ARM for Solaris.
* Tasking_CMX: CMX integration to debug with Tasking CrossView Pro on Windows.
* Gnu_Windows: Win32 integration to debug with Cygwin gdb on Windows.
* Gnu_Solaris: Posix integration to debug with gdb on Solaris.
* Gnu_Linux: Posix integration to debug with gdb on Linux.

