INSTALL.in 4.27 KB
Newer Older
1 2 3
Simple install procedure
========================

Matthias Clasen's avatar
Matthias Clasen committed
4 5
  % tar xf glib-@GLIB_VERSION@.tar.gz       # unpack the sources
  % cd glib-@GLIB_VERSION@                  # change to the toplevel directory
6 7
  % meson _build                            # configure the build
  % ninja -C _build                         # build GLib
8 9

  [ Become root if necessary ]
10
  % ninja -C _build install                 # install GLib
11 12 13 14

Requirements
============

15 16 17 18
GLib requires a C90-compliant (but not necessarily C99-compliant) C
compiler and libc. On UNIX-like systems, it also assumes compliance
with at least the original 1990 version of POSIX.

Owen Taylor's avatar
Owen Taylor committed
19 20 21 22 23 24 25 26
GLib-2.0 requires pkg-config, which is tool for tracking the
compilation flags needed for libraries. (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.) Information about pkg-config can be found at:

  http://www.freedesktop.org/software/pkgconfig/

27
Meson (http://mesonbuild.com/) is also required.
Owen Taylor's avatar
Owen Taylor committed
28

29 30 31
In order to implement conversions between character sets,
GLib requires an implementation of the standard iconv() routine.
Most modern systems will have a suitable implementation, however
Matthias Clasen's avatar
Matthias Clasen committed
32
many older systems lack an iconv() implementation. On such systems,
33 34
you must install the libiconv library. This can be found at:

Owen Taylor's avatar
Owen Taylor committed
35
 http://www.gnu.org/software/libiconv/
36 37 38

If your system has an iconv implementation but you want to use
libiconv instead, you can pass the --with-libiconv option to
Matthias Clasen's avatar
Matthias Clasen committed
39
configure. This forces libiconv to be used.
40 41 42

Note that if you have libiconv installed in your default include
search path (for instance, in /usr/local/), but don't enable
43
it, you will get an error while compiling GLib because the
44 45
iconv.h that libiconv installs hides the system iconv.

46
If you are using the native iconv implementation on Solaris
Matthias Clasen's avatar
Matthias Clasen committed
47
instead of libiconv, you'll need to make sure that you have
48 49 50 51 52
the converters between locale encodings and UTF-8 installed.
At a minimum you'll need the SUNWuiu8 package. You probably
should also install the SUNWciu8, SUNWhiu8, SUNWjiu8, and
SUNWkiu8 packages.

53 54
The native iconv on Compaq Tru64 doesn't contain support for
UTF-8, so you'll need to use GNU libiconv instead. (When
55
using GNU libiconv for GLib, you'll need to use GNU libiconv
56 57 58
for GNU gettext as well.) This probably applies to related
operating systems as well.

59
Finally, for message catalog handling, GLib requires an implementation
Owen Taylor's avatar
Owen Taylor committed
60 61 62 63 64 65
of gettext(). If your system doesn't provide this functionality,
you should use the libintl library from the GNU gettext package,
available from:

 http://www.gnu.org/software/gettext/

66
Support for extended attributes and SELinux in GIO requires
Matthias Clasen's avatar
Matthias Clasen committed
67 68 69 70 71
libattr and libselinux.

Some of the mimetype-related functionality in GIO requires the
update-mime-database and update-desktop-database utilities, which
are part of shared-mime-info and desktop-file-utils, respectively.
72

73
GObject uses libffi to implement generic marshalling functionality.
74

75 76 77
The Nitty-Gritty
================

Matthias Clasen's avatar
Matthias Clasen committed
78
Complete information about installing GLib can be found
79
in the file:
Matthias Clasen's avatar
Matthias Clasen committed
80

81
 docs/reference/glib/html/glib-building.html
Matthias Clasen's avatar
Matthias Clasen committed
82

83
Or online at:
Matthias Clasen's avatar
Matthias Clasen committed
84

85
 https://developer.gnome.org/glib/stable/glib-building.html
86 87 88 89 90 91 92 93 94 95 96 97 98


Installation directories
========================

The location of the installed files is determined by the --prefix
and --exec-prefix options given to configure. There are also more
detailed flags to control individual directories. However, the
use of these flags is not tested.

One particular detail to note, is that the architecture-dependent
include file glibconfig.h is installed in:

Owen Taylor's avatar
Owen Taylor committed
99
  $exec_prefix/lib/glib/include/
100 101 102 103

if you have a version in $prefix/include, this is out of date
and should be deleted.

Matthias Clasen's avatar
Matthias Clasen committed
104
.pc files for the various libraries are installed in
Owen Taylor's avatar
Owen Taylor committed
105
$exec_prefix/lib/pkgconfig to provide information when compiling
106
other packages that depend on GLib. If you set PKG_CONFIG_PATH
Matthias Clasen's avatar
Matthias Clasen committed
107
so that it points to this directory, then you can get the
Owen Taylor's avatar
Owen Taylor committed
108 109 110 111 112
correct include flags and library flags for compiling a GLib
application with:

 pkg-config --cflags glib-2.0
 pkg-config --libs glib-2.0
113

Owen Taylor's avatar
Owen Taylor committed
114 115 116 117

Cross-compiling GLib
====================

Matthias Clasen's avatar
Matthias Clasen committed
118
Information about cross-compilation of GLib can be found
119
in the file:
Matthias Clasen's avatar
Matthias Clasen committed
120

121
 docs/reference/glib/html/glib-cross-compiling.html
Matthias Clasen's avatar
Matthias Clasen committed
122

123
Or online at:
Matthias Clasen's avatar
Matthias Clasen committed
124

125
 https://developer.gnome.org/glib/stable/glib-cross-compiling.html