Configuration Options

From reSIProcate
Revision as of 17:26, 26 November 2008 by Adam (talk | contribs)
Jump to navigation Jump to search

Because the resiprocate project does not use GNU autotools, it has its own configuration system that can be used to select various options within the project, as well as what parts of the project are built. By default, if you just type 'make', the configuration script is invoked by the makesystem, and some (mostly) sane defaults are chosen for you.

However, if you want to take advantage of the advanced, new, and/or experimental features available within resiprocate, you really want to take advantage of the configuration system. Currently, you have three options:

  • ./configure - Invoke the configuration system in a text questionnaire mode. This can be tedious, but should work under all terminal environments.
  • ./configure -m - Invoke the configuration system in a (somewhat experimental) text-based menu mode. This is much easier to use, but requires a vt100-compatible that is tall enough to accommodate all the configuration options.
  • ./configure -y - Invoke the configuration system in a non-interactive mode. Configuration options will be set to defaults if they don't yet exist, and then any configuration-changing commandline switches will be applied. If the system is already configured, no options will be changed except as specified by commandline switches.


 ./configure [options]
     -y, --non-interactive
       Run non-interactively
     -m, --use-text-menu
       Run with text menu interface
       Which toolchain do you want to use? (Now "gnu")
       Valid values are: [gnu, intel, sunpro, msgnu, gnu-cross]
       What is the name your toolchain uses for the cross platform? (Now "arm-unknown-linux-gnu")
       What is the prefix for the cross-compiler binaries? (Now "arm-unknown-linux-gnu")
       Where is your cross compiler installed? (Now "/opt/crosstool/current/arm-unknown-linux-gnu/bin/")
       What compile profile will you use? (Now "debug")
       Valid values are: [debug, nodebug, opt, gopt, prof, small]
       Should the resip libraries be built shared? (Now disabled)
       Will you be using distcc? (Now disabled)
       Will you be using ccache? (Now disabled)
       Build the Repro proxy server? (Now enabled)
       Which database should be used with Repro? (Now "berkeley-db4")
       Valid values are: [berkeley-db4]
       Where is db_cxx.h? (Now "/opt/local/include/db42")
       Build the RADIUS authentication module? (requires radiusclient-ng) (Now disabled)
       Build the TFM test framework? (Now disabled)
       Build the reCon Conversation Manager? (requires dtls-srtp patched OpenSSL) (Now disabled)
       Build the reTurn client? (Now disabled)
       Build the reTurn server? (Now disabled)
       Where is boost/config.hpp? (Now "/opt/local/include")
       Are the sipX libraries and headers installed? (Now disabled)
       Where is the common root of the sipX libraries? (Now "../sipXtapi")
       Where are the sipX libraries installed? (Now "/usr/local/lib")
       Where are the sipX header files installed? (Now "/usr/local/include")
       Include SIP over TLS, SMIME or Identity header support? (Requires OpenSSL) (Now enabled)
       Do you want to include SIP over DTLS support? (Requires OpenSSL 0.9.8+) (Now disabled)
       Where is OpenSSL? (leave blank to use installed copy) (Now "")
       Should DUM use curl to retreive identity information? (Now disabled)
       Use the Google malloc() implementation? (Now disabled)
       Use Google cpuperf? (Now disabled)
       Compile in IPv6 support? (Now disabled)
       Use popt to read commandline options? (Now enabled)
       Where is popt.h? (Now "/usr/include")
       Where is libpopt? (Now "/usr/lib")
       Compile with no floating point functions? (Now disabled)
       Force stack to fully parse every message it receives? (Now disabled)
       Where should the libraries be installed? (Now "/usr/local")
       Which DNS resolution library do you want to use? (Now "resip-ares")
       Valid values are: [resip-ares, c-ares]
       Where should ares be installed? (Now "/usr/local")
       If using c-ares, the directory containing its headers. (Now "")
       If using c-ares, the directory containing its libraries. (Now "")