If you do not use either the development packages of your distribution or the source packages made by the upstream authors of dependencies, you may want to try our custom dependencies building script in tools/ directory:
Note that commoncpp, ccrtp, libosip and libexosip, samplerate are in debian and fedora.
You can also compile each dependency, one by one:
1/ For commoncpp2
./configure [option]
make
make install
2/ For ccrtp
./configure [option]
make
make install
3/ For libosip2
./configure [option]
make
make install
Note: if you install any package in /usr/local, don't forget to set pkg-config path with:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/
Building SFLPhone
-----------------
./configure
make
make install (as root)
Using SFLPhone
--------------
If you have the sflphone 0.3 or 0.4 release, copy the file sflphonerc
to sflphonedrc:
cp ~/.sflphone/sflphonerc ~/.sflphone/sflphonedrc
If you have an older version, remove your sflphonerc file located in
$HOME/.sflphone
1. Install the GTK GUI
2. Lauch sflphone interface, a setup window appears.
3. If you do have a SIP account, fill the SIP stuff where related. You can
use STUN too.
4. Save your settings, restart it. You're done.
A user's guide will be available on:
http://www.sflphone.org/doc/
What if it does not build?
--------------------------
- Try using the same versions of the libraries as we do.
See http://www.sflphone.org in section Downloads.
- Try using the same compilers as ours: gcc 4.1.0 on Fedora Linux Core 5
is known to work.
- If you have dependencies installed in unusual directories, try setting
the environment variable CXXFLAGS before building, for example:
export CXXFLAGS="-I/opt/include"
How to enable IAX support?
--------------------------
Go inside libs directory and execute ./libiax2.sh script.
Then, run ./configure with --enable-iax2 option.
Debugging SFLPhone
------------------
You can use the --with-debug option with configure
./configure --with-debug
make
Run-time troubleshooting
------------------------
- If errors occured when trying to load shared libraries, check that the
value of the environment variable LD_LIBRARY_PATH include the
directories containing the required libraries, eg: