Configuration Options

From reSIProcate
Revision as of 12:55, 23 January 2013 by Dpocock (talk | contribs)
Jump to navigation Jump to search

Autotools / UNIX build configuration (reSIProcate >= 1.8)

Here is a quick summary of how to do some things that were configurable with the legacy build system:

Library locations

If you have libraries in non-standard locations (e.g. /opt/something/lib instead of /usr/lib) then please add those locations to LDFLAGS when running configure.

This may be needed for any of the non-system libraries if you compile them yourself, e.g. libdb, radiusclient-ng, mysqlclient, openssl, boost, sipX, curl, popt or c-ares.


{{{ ./configure \

    LDFLAGS="-L/opt/csw/lib -L/opt/csw/bdb48/lib -DTHREAD=MULTI -mt -dalign -V -v"


Header locations

If you have headers (e.g. db_cxx.h) in non-standard locations (e.g/ /opt/something/include instead of /usr/include) then please add those locations to CPPFLAGS when running configure

This may be needed for any of the non-system libraries if you compile them yourself, e.g. libdb, radiusclient-ng, mysqlclient, openssl, boost, sipX, curl, popt or c-ares.


{{{ ./configure \

    CPPFLAGS="-I/opt/csw/include -I/opt/csw/bdb48/include -mt -V -v"


Using non-default compiler and tools or cross-compiling

If you want to use a compiler or cross-compiler other than the default compiler that autotools finds on your system, you can use the configure variables CC, CXX, LD, etc

Here is an example for using SunStudio on Solaris:

{{{ ./configure \

    CC=/opt/studio/sunstudio12.1/bin/cc \


Using distcc, ccache and other compiler wrappers

Setting CC and CXX also lets you invoke tools like distcc and ccache to speed up the compile

Just distcc:

{{{ export DISTCC_POTENTIAL_HOSTS="localhost host2 host3" ./configure \


pump make -j8 }}}

Just using ccache:

{{{ ./configure \


make }}}

Using distcc and ccache together:

{{{ export DISTCC_POTENTIAL_HOSTS="localhost host2 host3" ./configure \


CCACHE_PREFIX=distcc pump make -j8 }}}

Compile profiles (small builds, debug builds, optimised, etc)

The legacy configure offered some compiler profiles with common defaults.

Here are some examples of how to achieve similar behavior with autotools:

Debug vs non-debug builds

To turn off assert() processing in a production build, just add -DNDEBUG to CPPFLAGS, e.g.

./configure CPPFLAGS="-DNDEBUG"

Using Google malloc

Just add tcmalloc to LDFLAGS

{{{ ./configure LDFLAGS="-ltcmalloc" }}}

Using Google performance profiling libs

{{{ ./configure LDFLAGS="-lprofiler" }}}

Legacy UNIX build configuration (reSIProcate <= 1.7)

The legacy build system uses a custom configuration script 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.

Note that the defaults chosen for some options vary from platform to platform, and even according to what is installed on the system when configuration is invoked.

The various options currently available in the configuration system are:

       Which toolchain do you want to use?
       Valid values are: [gnu, intel, sunpro, msgnu, gnu-cross]
       What is the name your toolchain uses for the cross platform?
       What is the prefix for the cross-compiler binaries?
       Where is your cross compiler installed?
       What compile profile will you use?
       Valid values are: [debug, nodebug, opt, gopt, prof, small]
       Should the resip libraries be built shared?
       Should position-independent-code (PIC) be generated even when
       not building shared libraries? This only applies on x86_64/amd64
       architecture and only when NOT building shared libraries. When enabled,
       the generated static libraries will be PIC, and can then be linked
       into "jumbo" shared libraries.
       Will you be using distcc?
       Will you be using ccache?
       Build the Repro proxy server?
       Which database should be used with Repro?
       Valid values are: [berkeley-db4]
       Where is db_cxx.h?
       Build the RADIUS authentication module? (requires radiusclient-ng)
       Build the TFM test framework?
       Build the reCon Conversation Manager? (requires dtls-srtp patched OpenSSL)
       Build the reTurn client?
       Build the reTurn server?
       Where is boost/config.hpp?
       Are the sipX libraries and headers installed?
       Where is the common root of the sipX libraries?
       Where are the sipX libraries installed?
       Where are the sipX header files installed?
       Include SIP over TLS, SMIME or Identity header support? (Requires OpenSSL)
       Do you want to include SIP over DTLS support? (Requires OpenSSL 0.9.8+)
       Where is OpenSSL? (leave blank to use installed copy)
       Should DUM use curl to retreive identity information?
       Use the Google malloc() implementation?
       Use Thread Local Storage with random_r() to generate random numbers?
       See Random_number_generation for details.
       Use Google cpuperf?
       Compile in IPv6 support?
       Compile in stack support for epoll() system call?
       Enabled by default if system header file present.
       Use popt to read commandline options?
       Test apps and repro make use of popt.
       Where is popt.h?
       Where is libpopt?
       Compile with no floating point functions?
       Force stack to fully parse every message it receives?
       Where should the libraries be installed?
       Which DNS resolution library do you want to use?
       Valid values are: [resip-ares, c-ares]

Support for c-ares remains experimental. Note that using c-ares with resiprocate requires a bleeding-edge copy of c-ares at the moment. See the c-ares project page for information about obtaining a copy of c-ares from their cvs repository.

       Where should ares be installed?
       If using c-ares, the directory containing its headers.
       If using c-ares, the directory containing its libraries.