Installing from Source
You should only be building fldigi locally if the binary distribution
does not work on your Linux distribution. Unless you are
modifying the code or need to compile for debugging you will not have
any additional functionality over the binary files. The source
code for fldigi is very large and has a number of dependencies that
must be satisfied before a successful compile. If you are not
familiar with compiling and linking source code you should probably
practice on a simpler package before treading these waters.
The installation of Fldigi
from the source code tarball requires several, development libraries to be present and installed on
your system before you compile Fldigi, but it all goes together pretty seamlessly.
- Fast Light Tool Kit - FLTK
version 1.1.7 or greater.
- configure the compilation of Fltk as:
- ./configure --enable-threads --enable-xft --enable-localjpeg --enable-localpng --enable-localzlib
- then simply execute make and make install (make install as super user or use "sudo make install")
- if you already have an OS maintained fltk install that does not
include the above switches you will need to remove that package before
building a locally compiled and installed version. If you do not
you might end up with two conflicting library installs.
- Hamlib - Hamlib Library Source
the
latest release is 1.2.6. Fldigi has been compiled to work with
this release of hamlib to insure access to the latest updates to the
rig specific source code. Follow the
instruction in the source code top directory. The library must be
installed as super user. You should compile as your normal login
user. The alpha testers have reported that the precompiled hamlib
RPM and DEB distributions will work OK.
- boost - you only need the development headers
- portaudio and
portaudiocpp. Download and install the latest portaudio
development tarball then make and make install. Don't forget to
sudo when you make install. The portaudiocpp build is found in
the subdirectory bindings/cpp. Again you need to make and make
install.
- libsndfile - built and installed
- Be sure that your /etc/ld.so.conf file contains the following
line: /usr/local/lib. Then execute "sudo ldconfig". The
compiler/linker will then know where to find the libraries.
- Compile the fldigi source code:
- Untar the fldigi.src.tgz file to a convenient location on your hard drive. I like to keep all of my development code
in a single tree such as ~/development/fldigi for example.
- execute "make". This will create a new
directory named Install and Objects. The object files will be in Objects and the executable file
will be in Install.
- if you need to debug the problem then create a debug version with
"make CFG=hamlib-debug". This will create a gdb compatible version in the Install directory.
- copy the binary file Install/fldigi to a directory that your
shell can routinely access for executable files. I have a ~/bin
directory that holds all of my local executables.
- if you plan on using fldigi with pskmail then you
should create a separate directory directly under your $HOME directory.
It should be named "pskmail.files" and contain a single file
in it to start:
- PSKmailclient, or PSKmailserver, depending on your desired pskmail service.
- fldigi can then be executed from a command line or from a desktop icon and it will act as the transport layer for pskmail