Using command-line interface to build and run T-applications

The OpenTS command prompt can be run by clicking appropriate link in Start/All Programs/OpenTS folder. There are 3 types of prompt:

Open T-System Command Prompt (Win32): to build 32-bit applications under 32-bit and 64-bit OSes
Open T-System Command Prompt (AMD64): to build 64-bit applications under 64-bit OS
Open T-System Command Prompt (Cross Tools): to build 64-bit applications under 32-bit OS

Standard OpenTS installer copies not only necessary OpenTS libraries and tools, but also an example T++ program fib.tpp. This can be built right out of the box. Here are some examples.

Building fib.exe:
Running in uniprocessor (uni-core) mode. This run calculates the 20-th Fibonacci number.
T++ applications are indeed MPI applications having special runtime. So fib.exe can be run in parallel using 'mpiexec' tool, enabling 2 processor cores in this example:
It is possible to enable all processor cores not only by mpiexec, but also by means of T++ runtime. Consider the following example. A T-application here is run in native SMP mode by specifying the '-tct enableSMP' option:
Finally, T-applications can be run on compute cluster (if you have one) using Compute Cluster Job Manager. This tool is provided within Microsoft HPC Pack. A screenshot shows how to run T-application ep.exe on 3 nodes having 2 processor cores each.

Here is a complete list of compile options:

/auto-c-call — allows T-application to call C-versions of T-functions. This may dramatically increase productivity;
/c — only compilation of source files without linking;
/dbg — make debug build. It allows debugger to obtain information about program symbols in the case of application crush;
/do — specify location for object files;
/not — compile for sequential execution only, all T++ keywords are ignored;
/o — specify output executable;
/p — pass option to used C/C++ compiler;
/pl — pass option to used C/C++ linker;
/v — print build commands before invocation;