The Prosody distribution is typically downloaded using the Aculab Installer Tool (AIT).
Prosody is packaged so that it all unpacks into a single directory and that directory's name includes the version number of the software. This means that you can unpack any number of packages or versions of the same package into the same directory without any of them adding or overwriting files in another version.
In the documentation for Prosody, references to a file or directory are often in the form:
$(TiNG)/directory/ $(TiNG)/dir/file
The name $(TiNG) is used to refer to the directory
created by unpacking a distribution so, for example, if you unpack a
version called m123 and it creates a directory
TiNG-distm123. then $(TiNG)/test/play.c would
mean the file TiNG-distm123./test/play.c.
Some of the test programs use the APIs provided by the switch
driver and the call driver Both of these come in separate packages. They
should be put in directories beside the Prosody directory. For example,
if you put everything in a directory called aculab, you
might have directories:
aculab/TiNG-distm123. aculab/call-5.5.00 aculab/switch-3.2.0
On operating systems which support symbolic links (such as Solaris),
make a link so that the names TiNG, call,
and switch are each an alias for the version of each
package that you want to use. For example, the commands
ln -s TiNG-distm123. TiNG ln -s call-5.5.00 call ln -s switch-3.2.0 switch
would be suitable if the versions you have are those given in the example above.
For Windows NT, which does not support symbolic links, the best alternative is to rename the directory that was unpacked.
For Windows 2000 / XP, you can try using directory junctions, which are
very similar to symbolic links. Since no method is provided for creating
one, you'll need either LINKD.EXE from the Windows 2000
Resource Kit, or the free alternative called Junction from
Sysinternals (see
http://www.sysinternals.com/ntw2k/source/misc.shtml).
You are now ready to check the list of prerequisites before building.