Prosody guide: building applications with Visual Studio

There are two ways to use Prosody TiNG on Microsoft Windows:

1. Statically linking the API libraries
2. Dynamically linking the API libraries

These instructions assume you are using Microsoft Development Environment 2002 Version 7 or one of the later versions.

Statically Linking the APIs

• Enter the Properties... option from the Project menu
• Select the C/C++ / Code Generation items from the tree on the left
• Set Run-time library to Multithreaded (Debug Multithreaded if in debug mode)
• Change to C/C++ / General
• In the Additional include directories box add the location of the TiNG include directory (which will be C:\Program Files\Aculab\TiNG\include unless you selected a different location when installing the distribution).
• If you want to use the POSIX thread emulation (it is needed for the high level replay and record library and many of the test programs), in the Additional include directories box add the location of the TiNG include/libutil/WINNT directory (which will be C:\Program Files\Aculab\TiNG\include\libutil\WINNT unless you selected a different location when installing the distribution).
• Change to C/C++ / Preprocessor
• In the Preprocessor definitions box, add TiNGTYPE_WINNT
• Add the necessary files to the project depending on what APIs your program uses (you can safely add them all if you like - it will merely make the program slightly larger than necessary. The files you may need to add are:

  File	When required
  TiNG/apilib/TiNGcore.c	Needed if any Prosody functions are used.
  TiNG/apilib/prosody_x.c	Needed if any Prosody X card or Prosody S is opened
  TiNG/highapi/smclib.c	Needed if any high level conferencing Prosody functions are used.
  TiNG/highapi/smhlib.c	Needed if any high level replay and record Prosody functions are used.
  TiNG/highapi/smbfhlib.c	Needed if any BFILE high level replay and record Prosody functions are used.
  TiNG/highapi/smwavlib.c	Needed if any high level WAV file replay and record Prosody functions are used.
  TiNG/highapi/smbfwavlib.c	Needed if any high level WAV BFILE replay and record Prosody functions are used.
  TiNG/libutil/WINNT/pthread.c	Used by smhlib.c. Also needed if you use POSIX pthreads emulation (which allows you to use the same threads API on Windows and Linux).

Dynamically linking the APIs:

• Enter the Properties... option from the Project menu
• Select the C/C++ / Code Generation items from the tree on the left
• Set Run-time library to Multithreaded DLL
• Change to C/C++ / General
• In the Additional include directories box add the location of the TiNG include directory (which will be C:\Program Files\Aculab\TiNG\include unless you selected a different location when installing the distribution).
• If you want to use the POSIX thread emulation (it is needed for the high level replay and record library and many of the test programs), in the Additional include directories box add the location of the TiNG include/libutil/WINNT directory (which will be C:\Program Files\Aculab\TiNG\include\libutil\WINNT unless you selected a different location when installing the distribution).
• Change to C/C++ / Preprocessor
• In the Preprocessor definitions box, add TiNGTYPE_WINNT,TiNG_USE_DLL
• Change to Linker / Input
• In the Additional dependencies box add TiNG.lib
• Enter the Options... option from the Tools menu
• Select the Projects / VC++Directories tab
• Select Library files from the pull down list
• Add the paths for the TiNG.lib file and the TiNG.dll file. They can be in the same place (which will be C:\Program Files\Aculab\TiNG\lib\gen-WINNT_V6 unless you selected a different location when installing the distribution).

Note that if you link with a TiNG.lib file but run the application such that Windows finds an incompatible TiNG.dll and tries to use it, you may get errors complaining that functions were not found. This is because the .DLL and .LIB files use a mechanism to protect against incompatible changes. See also Prosody TiNG: Using the API DLL for further information.

Compiling the Test Programs

You can compile the test programs either statically or dynamically as described above.

• Create a new Win32 Console Application project
• Add the .c file, which you would like to compile
• Configure the project for static or dynamic linking as described above. If you are statically linking you can see which libraries are required by looking in the .c source file for the library headers it #includes.
• Add any other necessary source files, these will normally be found in the TiNG\libutil, TiNG\libutil\WINNT, or TiNG\test\Testlib directories.