|Midgard2 Reference Manual|
Compiling Midgard library
Compiling Midgard library — How to compile Midgard library
On UNIX, Midgard 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 Midgard library is thus:
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.
Before you can compile the Midgard library, you need to have various other tools and libraries installed on your system. The two tools needed during the build process (as differentiated from the tools used in when creating Midgard mentioned above such as autoconf) are pkg-config and GNU make.
is a tool for tracking the compilation flags needed for
libraries that are used by the Midgard library. (For each
library, a small
.pc text file is i
installed in a standard location that contains the compilation
flags needed for that library along with version number
information.) Configure script checks if pkg-config
version is correct.
GNU make.It may be called make or gmake.
Midgard library depends on a number of other libraries.
In addition to the normal options, the configure script in the Midgard library supports these additional arguments:
configure [[--with-libgda4=[no|yes]]] [[--with-dbus-support=[yes|no]]]
By default Midgard library is build with libgda3 support.
However, you may enable libgda4 by passing yes to this configure option.
Note, that libgda4 support is experimental and should not be used in production environmnent.
Default beheviour is to support D-Bus. No D-Bus message is sent from Midgard library when D-Bus support is disabled.