INSTALL 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  1. BUILD REQUIREMENTS
  2. ==================
  3. The UniMRCP project depends on a number of third party tools and libraries which must be installed first.
  4. All the required dependencies are available to download prepackaged for the UniMRCP use from the
  5. following location:
  6. http://www.unimrcp.org/downloads/dependencies
  7. Alternatively, original versions of the libraries as well as patches on them can be downloaded
  8. separately from the following location:
  9. http://www.unimrcp.org/dependencies
  10. References:
  11. 1. Apache Portable Runtime [>=1.2.x] (http://apr.apache.org).
  12. In order to build any part of the UniMRCP project, the Apache Portable Runtime (APR) and
  13. the APR Utility (APR-util) libraries are required. The libraries provide a consistent interface to
  14. underlying platform-specific implementations.
  15. 2. Sofia-SIP [>=1.12.6] (http://sofia-sip.sourceforge.net).
  16. Sofia-SIP is an open-source SIP User-Agent library, compliant with the IETF RFC3261 specification.
  17. The library is utilized for implementation of SIP signaling for MRCPv2. The SDP message parser is
  18. also used for both MRCPv2 (SIP/SDP) and MRCPv1 (RTSP/SDP).
  19. GNU BUILD
  20. =========
  21. Prerequisites:
  22. autoconf 2.59 or newer
  23. automake
  24. libtool 1.4 or newer
  25. gcc
  26. pkg-config
  27. Procedure:
  28. If the UniMRCP source is checked out from the repository, the "bootstrap" script must be run first
  29. in order to generate the "configure" script and other required files.
  30. ./bootstrap
  31. The usual "configure", "make", "make install" sequence of commands should follow in order to build
  32. and install the project from source.
  33. ./configure
  34. make
  35. make install
  36. As a result, the project will be installed in the directory "/usr/local/unimrcp" with the following
  37. layout:
  38. bin binaries (unimrcpserver, unimrcpclient, ...)
  39. conf configuration files (unimrcpserver.xml, unimrcpclient.xml, ...)
  40. data data files
  41. include header files
  42. lib shared (convenience) libraries
  43. log log files
  44. plugin run-time loadable modules
  45. There are a couple of options which can additionally be configured.
  46. In order to specify where to look for the APR and APR-util libraries, use the "--with-apr=" and
  47. "--with-apr-util=" options respectively. For example:
  48. ./configure --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr
  49. In order to specify where to look for the Sofia-SIP library, use the "--with-sofia-sip=" option.
  50. For example:
  51. ./configure --with-sofia-sip=/usr/local/sofia-sip
  52. In order to generate executables and shared libraries for x86-64 architecture, use the "-m64"
  53. option as follows:
  54. CFLAGS=-m64 CXXFLAGS=-m64 LDFLAGS=-m64 ./configure
  55. In order to generate executables and shared libraries for i386 architecture, use the "-m32" option
  56. as follows:
  57. CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32 ./configure
  58. In order to install the default configuration, use the following commands:
  59. cd conf
  60. make def-conf
  61. In order to install the default data files, use the following commands:
  62. cd data
  63. make def-data
  64. In order to build a Doxygen generated documentation, use the following command:
  65. make dox
  66. WINDOWS BUILD
  67. =============
  68. Prerequisites:
  69. Microsoft Visual Studio 2005 or 2010.
  70. One-time pre-build setup: [optional]
  71. This step can be skipped if the dependencies are installed in their default locations. Otherwise,
  72. the paths in the corresponding property sheets must be modified accordingly. Below is the content
  73. of property sheets for Visual Studio 2005, which are located in the directory "build/vsprops".
  74. Similarly, property sheets for Visual Studio 2010 can be found in the directory "build/props".
  75. apr.vsprops
  76. <UserMacro
  77. Name="AprDir"
  78. Value="$(SolutionDir)libs\apr"
  79. />
  80. <UserMacro
  81. Name="AprUtilDir"
  82. Value="$(SolutionDir)libs\apr-util"
  83. />
  84. sofiasip.vsprops
  85. <UserMacro
  86. Name="SofiaDir"
  87. Value="$(SolutionDir)libs\sofia-sip"
  88. />
  89. Procedure:
  90. 1. Open one of the available solution files:
  91. * for Visual Studio 2005, use unimrcp.sln,
  92. * for Visual Studio 2010, use unimrcp-2010.sln.
  93. 2. Choose a platform (Build -> Configuration Manager):
  94. * win32
  95. * x64.
  96. 3. Choose a configuration (Build -> Configuration Manager):
  97. * Debug
  98. * Release.
  99. 4. Build the solution (Build -> Build Solution).
  100. One-time output directory setup:
  101. Build the "prepare.vcproj" utility project by right clicking on the project icon from the Solution
  102. Explorer (tools->prepare) and selecting the Build command from the context menu. This routine will
  103. setup the output directory and copy all the required APR, APR-Util, and Sofia-SIP libraries as well
  104. as the default configuration and data files. As a result, the output directory layout will look
  105. like the following:
  106. bin binaries (unimrcpserver, unimrcpclient, ...) and all the required dlls
  107. conf configuration files (unimrcpserver.xml, unimrcpclient.xml, ...)
  108. data data files
  109. lib libraries
  110. log log files
  111. plugin run-time loadable modules