Jul 07 2014
The UniMRCP project depends on a number of third party tools and libraries which must be installed first.
All the required dependencies are available to download prepackaged for the UniMRCP use from the
Alternatively, original versions of the libraries as well as patches on them can be downloaded
separately from the following location:
1. Apache Portable Runtime [>=1.2.x] (http://apr.apache.org).
In order to build any part of the UniMRCP project, the Apache Portable Runtime (APR) and
the APR Utility (APR-util) libraries are required. The libraries provide a consistent interface to
underlying platform-specific implementations.
2. Sofia-SIP [>=1.12.6] (http://sofia-sip.sourceforge.net).
Sofia-SIP is an open-source SIP User-Agent library, compliant with the IETF RFC3261 specification.
The library is utilized for implementation of SIP signaling for MRCPv2. The SDP message parser is
also used for both MRCPv2 (SIP/SDP) and MRCPv1 (RTSP/SDP).
Microsoft Visual Studio 2005 or 2010.
One-time pre-build setup: [optional]
This step can be skipped if the dependencies are installed in their default locations. Otherwise,
the paths in the corresponding property sheets must be modified accordingly. Below is the content
of property sheets for Visual Studio 2005, which are located in the directory "build/vsprops".
Similarly, property sheets for Visual Studio 2010 can be found in the directory "build/props".
1. Open one of the available solution files:
* for Visual Studio 2005, use unimrcp.sln,
* for Visual Studio 2010, use unimrcp-2010.sln.
2. Choose a platform (Build -> Configuration Manager):
3. Choose a configuration (Build -> Configuration Manager):
4. Build the solution (Build -> Build Solution).
One-time output directory setup:
Build the "prepare.vcproj" utility project by right clicking on the project icon from the Solution
Explorer (tools->prepare) and selecting the Build command from the context menu. This routine will
setup the output directory and copy all the required APR, APR-Util, and Sofia-SIP libraries as well
as the default configuration and data files. As a result, the output directory layout will look
like the following:
bin binaries (unimrcpserver, unimrcpclient, ...) and all the required dlls
conf configuration files (unimrcpserver.xml, unimrcpclient.xml, ...)
data data files
log log files
plugin run-time loadable modules