Compiling the Spread RPC library

Compiling the Spread RPC library — How to compile Spread RPC library itself

Building the Library on UNIX

On UNIX, Spread RPC library uses the standard GNU build system, using autoconf for package configuration and resolving portability issues, automake for building makefiles that comply with the GNU Coding Standards, and libtool for building shared libraries on multiple platforms. The normal sequence for compiling and installing the Spread RPC library is thus:

          ./configure
          make
          make install

The standard options provided by GNU autoconf may be passed to the configure script. Please see the autoconf documentation or run ./configure --help for information about the standard options.

Dependencies

Before you can compile the Spread RPC library, you need to have various other tools and libraries installed on your system:

pkg-config is a tool for tracking the compilation flags needed for libraries that are used by the Spread RPC library. (For each library, a small .pc text file is installed in a standard location that contains the compilation flags needed for that library along with version number information.) The version of pkg-config needed to build SpreadRPC is mirrored in the dependencies directory on the GTK+ FTP site.
GLib is a general-purpose utility library, which provides many useful data types, macros, type conversions, string utilities, file utilities, a main loop abstraction, and so on. It works on many UNIX-like platforms, Windows, OS/2 and BeOS. GLib is released under the GNU Library General Public License (GNU LGPL).

The general policy of GLib is that all functions are invisibly threadsafe with the exception of data structure manipulation functions, where, if you have two threads manipulating the same data structure, they must use a lock to synchronize their operation.