Installation Instructions for fldigi
To compile fldigi you will need:
* A recent C++ compiler. The GNU C++ compilers in the 4.x series are
known to work.
* Version 1.1.x of the Fast Light Tool Kit (FLTK), with its
development library and headers. Versions 1.1.7 to 1.1.9 are known
to work. FLTK's multi-threading support is required.
* The samplerate (a.k.a. secret rabbit code) library.
* The PNG library.
You should also install the libraries and headers for PortAudio, the
Portable audio I/O library.
Additional features are enabled if the corresponding libraries are
present on your system:
* Support for rig control via hamlib is enabled if the hamlib
development files are installed.
* Audio file generation, capture and playback support is enabled if
`configure' can find the sndfile library.
* The PulseAudio sound backend is compiled if the development files
for libpulse-simple, the PulseAudio simple API library, are present.
Once you have installed the required packages, the following commands
should be sufficient to compile fldigi and install it under /usr/local:
make install (you may need superuser privileges for installation)
The `install' target installs the executables, icons, .desktop files and
manual pages. After installation, an fldigi launcher should appear
somewhere in your applications menu.
If you are building a GIT snapshot (see README), you will need to run
`autoreconf' to generate the configure script.
Mac OS X installation notes
Mac OS X support was added in version 2.10. To run fldigi on OS X, you
will need to create an app bundle. For this purpose, the Makefile has
an `appbundle' target that can be used instead of `install':
This target will generate two bundles inside the build directory (by
* mac-bundle/fldigi.app, which only contains the bare minimum that is
required to run fldigi on the build system
* mac-libs-bundle/fldigi.app, which also includes copies of non-system
libraries (such as PortAudio and FLTK) that the binary links to
The configure script has some support for building universal x86/ppc
binaries. Pass the following additional arguments to enable it:
See this page for more information:
Windows installation notes
As of version 3.12, Cygwin is not required to build or run fldigi.
Refer to this page for Mingw32 build information:
Building under Cygwin should still work but is not supported. To
install Cygwin, use the following installer link:
Refer to the list of library requirements and install the corresponding
cygwin packages. You will need at least the following:
Base: (all base packages)
Devel: binutils fltk-devel gcc-g++ make pkg-config
Graphics: libjpeg-devel libpng12-devel
Use the default "Curr" option for the package selection.
To build an internationalized version of fldigi, install these
gettext gettext-devel libiconv libiconv2
PortAudio and libsamplerate are not available from Cygwin and must be
compiled from source. If you wish to build easily redistributable
binaries, configure these libraries for static linking, e.g. with
After you have installed them in the desired location, remember to tell
`pkg-config' how to find them, e.g. with
To configure fldigi itself for static linking, use the following
./configure --enable-static LDFLAGS=-static
This will produce a binary that only depends on the cygwin library,
which can be found in /bin/cygwin1.dll.
At the time of writing, fldigi has been built with the latest release of
Cygwin, version 1.5.25. The binary runs on Windows 2000 and XP,
however, a newer version of the cygwin1.dll library may be required for
Vista. Version 20080530 of the 1.7 pre-release snapshot has been tested
and is known to work:
========== Generic installation instructions follow ==========
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006 Free Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You need `configure.ac' if
you want to change it or regenerate `configure' using a newer version
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug. Until the bug is fixed you can use this workaround:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' recognizes the following options to control how it operates.
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
Alias for `--cache-file=config.cache'.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.