Many distributions come with prebuilt Gammu binaries, if you can use them, it is definitely the easiest thing. There are also binary packages of latest release built for many distributions available on Gammu home page <http://wammu.eu/gammu/>.
You can usually also find Gammu in your distribution, so unless you need a newer version, just install package from your distribution.
Gammu packages are included in Debian (testing versions go to experimental and stable to unstable). If you want to build Debian package on your own, you can find packaging in Git repository at git://git.debian.org/git/collab-maint/gammu.git (you can browse it on <http://git.debian.org/?p=collab-maint/gammu.git>).
Gammu packages are included in openSUSE and Fedora. Additionally source tarball contains gammu.spec which you can use for building RPM package.
Gammu packages are included in Gentoo. Additionally source tarball contains description-pak which you can use for building Slackware package.
You can download Windows binaries from <http://wammu.eu/gammu/>. For Windows 95, 98 and NT 4.0 you will also need ShFolder DLL, which can be downloaded from Microsoft:
You need CMake from <http://www.cmake.org/> for compiling Gammu.
Additionally pkg-config <http://pkg-config.freedesktop.org/> is used for detecting available libraries.
Gammu does not require any special libraries at all to build, but you might miss some features. Optional libraries include:
Required for fbususb/dku2 connection support on Linux.
Used to support more character sets in AT engine.
Not needed on platforms having native ODBC support such as Microsoft Windows.
Required at least version 0.8.2.
Needed for testing of SMSD using libdbi driver (libdbd-sqlite3), see Testing Gammu.
First install all Dependencies and Optional Dependencies. Do not forget to install corresponding devel packages as well, they are usually named with -dev or -devel suffix, depending on your distribution.
For example on Debian or Ubuntu, you can install all optional packages by following command:
apt-get install cmake python-dev pkg-config libmysqlclient-dev libpq-dev \ libcurl4-gnutls-dev libusb-1.0-0-dev libdbi0-dev libbluetooth-dev \ libgudev-1.0-dev libglib2.0-dev unixodbc-dev
For openSUSE, the installation all optional packages could look like:
zypper install libusb-1_0-devel libdbi-devel bluez-devel postgresql-devel \ mysql-devel python-devel libcurl-devel cmake pkgconfig unixODBC-devel \ glib2-devel libgudev-1_0-devel
For compatibility reasons, configure like wrapper is provided, if you don’t need much specific tuning, you can use usual set of commands:
./configure make sudo make install
The configure wrapper will create directory build-configure and build all binaries there (nothing is changed in source tree), for example gammu binary is in build-configure/gammu directory.
If you need/want to tweak build a bit more than configure wrapper provides, you have to use CMake directly. For now, only out of source build is supported, so you have to create separate directory for build:
mkdir build cd build
Then just configure project:
Test that everything is okay:
And finally install it:
sudo make install
You can configure build parameters either by command line (see parameters bellow), or using TUI - ccmake.
Useful cmake parameters:
You can also disable support for whole set of phones, e.g.:
By installing Gammu to non default system paths, you might need to add path where libGammu and other Gammu liraries are installed to ldconfig search path.
You can do this by editing /etc/ld.so.conf or adding new file to /etc/ld.so.conf.d/ directory containing path, wherge Gammu library has been installed. Some examples:
# Gammu on 64-bit Fedora installed to /opt/gammu echo /opt/gammu/lib64 > /etc/ld.so.conf.d/gammu.conf # Gammu installed to /usr/local echo /usr/local/lib > /etc/ld.so.conf.d/gammu.conf
The similar situation exists with Python modules, if you install in path when your Python interpreter does not search it won’t load newly installed Gammu bindings.
You can also avoid changing ldconfig configuration by installing Gammu to paths where it already searches, for examble by:
cmake .. -DCMAKE_INSTALL_PREFIX="/usr"
CMake is able to generate projects for various tools including Microsoft Visual Studio, Borland toolchains, Cygwin or Mingw32. Just click on CMakeLists.txt in project sources and configure CMake to be able to find optional libraries (see cross compilation section for more information about getting those). The result should be project for your compiler where you should be able to work with it as with any other project.
You will probably need additional SDKs:
After downloading and installing them into your system:
Borland toolchain - you can download compiler at <http://www.codegear.com/downloads/free/cppbuilder>. You need to add c:/Borland/BCC55/Bin to system path (or manually set it when running CMake) and add -Lc:/Borland/BCC55/Lib -Ic:/Borland/BCC55/Include -Lc:/Borland/BCC55/Lib/PSDK to CMAKE_C_FLAGS in CMake (otherwise compilation fails).
This should work pretty much same as on Linux.
Gammu should be compilable on Mac OS X, you need to have installed Developer Tols (version 2.4.1 was tested) and CMake (there is a Mac OS X “Darwin” DMG download). For database support in SMSD, install wanted database, eg. MySQL.
The rest of the compilation should be pretty same as on Linux, see Linux section for more details about compile time options.
If you get some errors while linking with iconv, it is caused by two incompatible iconv libraries available on the system. You can override the library name:
cmake -D ICONV_LIBRARIES="/opt/local/lib/libiconv.dylib" ..
Or completely disable iconv support:
cmake -DWITH_Iconv=OFF ..
To build backward compatible binaries, you need CMake 2.8 or newer. The command line then would look like:
cmake -DCMAKE_OSX_ARCHITECTURES="ppc;i386;x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET=10.4
Only cross compilation using CMake has been tested. You need to install MinGW cross tool chain and run time. On Debian you can do it by apt-get install mingw32. Build is then quite simple:
mkdir build-win32 cd build-win32 cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/Toolchain-mingw32.cmake make
There is also toolchain configuration for Win64 available:
mkdir build-win64 cd build-win64 cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/Toolchain-mingw64.cmake make
If your MinGW cross compiler binaries are not found automatically, you can specify their different names in cmake/Toolchain-mingw32.cmake.
To build just bare static library without any dependencies, use:
cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/Toolchain-mingw32.cmake \ -DBUILD_SHARED_LIBS=OFF \ -DWITH_MySQL=OFF \ -DWITH_Postgres=OFF \ -DWITH_GettextLibs=OFF \ -DWITH_Iconv=OFF \ -DWITH_CURL=OFF
To be compatible with current Python on Windows, we need to build against matching Microsoft C Runtime library. For Python 2.4 and 2.5 MSVCR71 was used, for Python 2.6 the right one is MSVCR90. To achieve building against different MSVCRT, you need to adjust compiler specifications, example is shown in cmake/mingw.spec, which is used by CMakeLists.txt. You might need to tune it for your environment.
The easies way to link with third party libraries is to add path to their installation to cmake/Toolchain-mingw32.cmake or to list these paths in CMAKE_FIND_ROOT_PATH when invoking cmake.
You can download MySQL binaries from <http://dev.mysql.com/>, but then need some tweaks:
cd mysql/lib/opt reimp.exe -d libmysql.lib i586-mingw32msvc-dlltool --kill-at --input-def libmysql.def \ --dllname libmysql.dll --output-lib libmysql.a
reimp.exe is part of mingw-utils and can be run through wine, I didn’t try to compile native binary from it.
You can download PostgreSQL binaries from <http://www.postgresql.org/>, but then you need to add wldap32.dll library to bin.
For Gettext (internationalization support), you need gettext-0.14.4-bin.zip, gettext-0.14.4-dep.zip, gettext-0.14.4-lib.zip from <http://gnuwin32.sourceforge.net/>. Unpack these to same directory.
To cross compile Gammu to different architecture (or platform) you need to provide CMake toolchain file for that and invoke CMake with it:
cmake -DCMAKE_TOOLCHAIN_FILE=~/Toolchain-eldk-ppc74xx.cmake ..
The build system accepts wide range of options. You can see them all by running GUI version of CMake or by inspecting CMakeCache.txt in build directory.
By setting following flags you can control which additional parts will be installed:
If there is some build failure (eg. some dependencies are not correctly detected), please attach CMakeCache.txt, CMakeFiles/CMakeError.log and CMakeFiles/CMakeOutput.log files to the report. It will help diagnose what was detected on the system and possibly fix these errors.
To find out what is going on during compilation, add -DCMAKE_VERBOSE_MAKEFILE=ON to cmake command line or run make with VERBOSE=1:
To debug program crashes, you might want to build Gammu with -DENABLE_PROTECTION=OFF, otherwise debugging tools are somehow confused with protections GCC makes and produce bogus back traces.
Currently python-gammu is distributed together with Gammu, so all you need to get it is to build Gammu with Python support (it should be automatically detected if you have development environment installed for Python).
Gammu uses CMake to generate build environment (for example Makefiles for UNIX, Visual Studio projects, Eclipse projects, etc.) which you can later use for building. You can use -DBUILD_PYTHON=/path/to/python to define path to another Python interpreter to use than default one available in the system.
Alternatively you can use standard distutils, for which setup.py is placed in python subdirectory.