Update requirements

Mention that the mimetype-functionality of GIO reqires update-mime-database
and update-desktop-database at runtime. (#577128)
This commit is contained in:
Matthias Clasen 2009-04-02 23:57:59 -04:00
parent 20774c5663
commit 82a5f787d6
2 changed files with 56 additions and 50 deletions

View File

@ -26,14 +26,14 @@ GNU make (http://www.gnu.org/software/make) is also recommended.
In order to implement conversions between character sets, In order to implement conversions between character sets,
GLib requires an implementation of the standard iconv() routine. GLib requires an implementation of the standard iconv() routine.
Most modern systems will have a suitable implementation, however Most modern systems will have a suitable implementation, however
many older systems lack an iconv() implementation. On such systems, many older systems lack an iconv() implementation. On such systems,
you must install the libiconv library. This can be found at: you must install the libiconv library. This can be found at:
http://www.gnu.org/software/libiconv/ http://www.gnu.org/software/libiconv/
If your system has an iconv implementation but you want to use If your system has an iconv implementation but you want to use
libiconv instead, you can pass the --with-libiconv option to libiconv instead, you can pass the --with-libiconv option to
configure. This forces libiconv to be used. configure. This forces libiconv to be used.
Note that if you have libiconv installed in your default include Note that if you have libiconv installed in your default include
search path (for instance, in /usr/local/), but don't enable search path (for instance, in /usr/local/), but don't enable
@ -41,7 +41,7 @@ it, you will get an error while compiling GLib because the
iconv.h that libiconv installs hides the system iconv. iconv.h that libiconv installs hides the system iconv.
If you are using the native iconv implementation on Solaris If you are using the native iconv implementation on Solaris
instead of libiconv, you'll need to make sure that you have instead of libiconv, you'll need to make sure that you have
the converters between locale encodings and UTF-8 installed. the converters between locale encodings and UTF-8 installed.
At a minimum you'll need the SUNWuiu8 package. You probably At a minimum you'll need the SUNWuiu8 package. You probably
should also install the SUNWciu8, SUNWhiu8, SUNWjiu8, and should also install the SUNWciu8, SUNWhiu8, SUNWjiu8, and
@ -62,19 +62,23 @@ available from:
Support for extended attributes and SELinux in GIO requires Support for extended attributes and SELinux in GIO requires
libattr and libselinux. 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.
The Nitty-Gritty The Nitty-Gritty
================ ================
Complete information about installing GLib can be found Complete information about installing GLib can be found
in the file: in the file:
docs/reference/glib/html/glib-building.html docs/reference/glib/html/glib-building.html
Or online at: Or online at:
http://developer.gnome.org/doc/API/2.0/glib/glib-building.html http://developer.gnome.org/doc/API/2.0/glib/glib-building.html
@ -94,10 +98,10 @@ include file glibconfig.h is installed in:
if you have a version in $prefix/include, this is out of date if you have a version in $prefix/include, this is out of date
and should be deleted. and should be deleted.
.pc files for the various libraries are installed in .pc files for the various libraries are installed in
$exec_prefix/lib/pkgconfig to provide information when compiling $exec_prefix/lib/pkgconfig to provide information when compiling
other packages that depend on GLib. If you set PKG_CONFIG_PATH other packages that depend on GLib. If you set PKG_CONFIG_PATH
so that it points to this directory, then you can get the so that it points to this directory, then you can get the
correct include flags and library flags for compiling a GLib correct include flags and library flags for compiling a GLib
application with: application with:
@ -108,9 +112,11 @@ application with:
Cross-compiling GLib Cross-compiling GLib
==================== ====================
Information about cross-compilation of GLib can be found Information about cross-compilation of GLib can be found
in the file: in the file:
docs/reference/glib/html/glib-cross-compiling.html docs/reference/glib/html/glib-cross-compiling.html
Or online at: Or online at:
http://library.gnome.org/devel/glib/stable/glib-cross-compiling.html

View File

@ -43,17 +43,17 @@ Notes about GLib 2.18
===================== =====================
* The recommended way of using GLib has always been to only include the * The recommended way of using GLib has always been to only include the
toplevel headers glib.h, glib-object.h and gio.h. GLib enforces this by toplevel headers glib.h, glib-object.h and gio.h. GLib enforces this by
generating an error when individual headers are directly included. generating an error when individual headers are directly included.
To help with the transition, the enforcement is not turned on by To help with the transition, the enforcement is not turned on by
default for GLib headers (it is turned on for GObject and GIO). default for GLib headers (it is turned on for GObject and GIO).
To turn it on, define the preprocessor symbol G_DISABLE_SINGLE_INCLUDES. To turn it on, define the preprocessor symbol G_DISABLE_SINGLE_INCLUDES.
Notes about GLib 2.16 Notes about GLib 2.16
===================== =====================
* GLib now includes GIO, which adds optional dependencies against libattr * GLib now includes GIO, which adds optional dependencies against libattr
and libselinux for extended attribute and SELinux support. Use and libselinux for extended attribute and SELinux support. Use
--disable-xattr and --disable-selinux to build without these. --disable-xattr and --disable-selinux to build without these.
Notes about GLib 2.10 Notes about GLib 2.10
@ -67,18 +67,18 @@ Notes about GLib 2.10
* The Unicode support has been updated to Unicode 4.1. This adds several * The Unicode support has been updated to Unicode 4.1. This adds several
new members to the GUnicodeBreakType enumeration. new members to the GUnicodeBreakType enumeration.
* The support for Solaris threads has been retired. Solaris has provided * The support for Solaris threads has been retired. Solaris has provided
POSIX threads for long enough now to have them available on every POSIX threads for long enough now to have them available on every
Solaris platform. Solaris platform.
* 'make check' has been changed to validate translations by calling * 'make check' has been changed to validate translations by calling
msgfmt with the -c option. As a result, it may fail on systems with msgfmt with the -c option. As a result, it may fail on systems with
older gettext implementations (GNU gettext < 0.14.1, or Solaris gettext). older gettext implementations (GNU gettext < 0.14.1, or Solaris gettext).
'make check' will also fail on systems where the C compiler does not 'make check' will also fail on systems where the C compiler does not
support ELF visibility attributes. support ELF visibility attributes.
* The GMemChunk API has been deprecated in favour of a new 'slice * The GMemChunk API has been deprecated in favour of a new 'slice
allocator'. See the g_slice documentation for more details. allocator'. See the g_slice documentation for more details.
* A new type, GInitiallyUnowned, has been introduced, which is * A new type, GInitiallyUnowned, has been introduced, which is
intended to serve as a common implementation of the 'floating reference' intended to serve as a common implementation of the 'floating reference'
@ -117,20 +117,20 @@ Notes about GLib 2.6.0
consideration, and use the gstdio wrappers to access files whose consideration, and use the gstdio wrappers to access files whose
names have been constructed from strings returned from GLib. names have been constructed from strings returned from GLib.
* Likewise, g_get_user_name() and g_get_real_name() have been changed * Likewise, g_get_user_name() and g_get_real_name() have been changed
to return UTF-8 on Windows, while keeping the old semantics for to return UTF-8 on Windows, while keeping the old semantics for
applications compiled against older versions of GLib. applications compiled against older versions of GLib.
* The GLib uses an '_' prefix to indicate private symbols that * The GLib uses an '_' prefix to indicate private symbols that
must not be used by applications. On some platforms, symbols beginning must not be used by applications. On some platforms, symbols beginning
with prefixes such as _g will be exported from the library, on others not. with prefixes such as _g will be exported from the library, on others not.
In no case can applications use these private symbols. In addition to that, In no case can applications use these private symbols. In addition to that,
GLib+ 2.6 makes several symbols private which were not in any installed GLib+ 2.6 makes several symbols private which were not in any installed
header files and were never intended to be exported. header files and were never intended to be exported.
* To reduce code size and improve efficiency, GLib, when compiled * To reduce code size and improve efficiency, GLib, when compiled
with the GNU toolchain, has separate internal and external entry with the GNU toolchain, has separate internal and external entry
points for exported functions. The internal names, which begin with points for exported functions. The internal names, which begin with
IA__, may be seen when debugging a GLib program. IA__, may be seen when debugging a GLib program.
* On Windows, GLib no longer opens a console window when printing * On Windows, GLib no longer opens a console window when printing
@ -139,22 +139,22 @@ Notes about GLib 2.6.0
stderr if you need to see them. stderr if you need to see them.
* The child watch functionality tends to reveal a bug in many * The child watch functionality tends to reveal a bug in many
thread implementations (in particular the older LinuxThreads thread implementations (in particular the older LinuxThreads
implementation on Linux) where it's not possible to call waitpid() implementation on Linux) where it's not possible to call waitpid()
for a child created in a different thread. For this reason, for for a child created in a different thread. For this reason, for
maximum portability, you should structure your code to fork all maximum portability, you should structure your code to fork all
child processes that you want to wait for from the main thread. child processes that you want to wait for from the main thread.
* A problem was recently discovered with g_signal_connect_object(); * A problem was recently discovered with g_signal_connect_object();
it doesn't actually disconnect the signal handler once the object being it doesn't actually disconnect the signal handler once the object being
connected to dies, just disables it. See the API docs for the function connected to dies, just disables it. See the API docs for the function
for further details and the correct workaround that will continue to for further details and the correct workaround that will continue to
work with future versions of GLib. work with future versions of GLib.
How to report bugs How to report bugs
================== ==================
Bugs should be reported to the GNOME bug tracking system. Bugs should be reported to the GNOME bug tracking system.
(http://bugzilla.gnome.org, product glib.) You will need (http://bugzilla.gnome.org, product glib.) You will need
to create an account for yourself. to create an account for yourself.
@ -167,12 +167,12 @@ In the bug report please include:
And anything else you think is relevant. And anything else you think is relevant.
* How to reproduce the bug. * How to reproduce the bug.
If you can reproduce it with one of the test programs that are built If you can reproduce it with one of the test programs that are built
in the tests/ subdirectory, that will be most convenient. Otherwise, in the tests/ subdirectory, that will be most convenient. Otherwise,
please include a short test program that exhibits the behavior. please include a short test program that exhibits the behavior.
As a last resort, you can also provide a pointer to a larger piece As a last resort, you can also provide a pointer to a larger piece
of software that can be downloaded. of software that can be downloaded.
* If the bug was a crash, the exact text that was printed out * If the bug was a crash, the exact text that was printed out
@ -192,7 +192,7 @@ Otherwise, enter a new bug report that describes the patch,
and attach the patch to that bug report. and attach the patch to that bug report.
Bug reports containing patches should include the PATCH keyword Bug reports containing patches should include the PATCH keyword
in their keyword fields. If the patch adds to or changes the GLib in their keyword fields. If the patch adds to or changes the GLib
programming interface, the API keyword should also be included. programming interface, the API keyword should also be included.
Patches should be in unified diff form. (The -u option to GNU Patches should be in unified diff form. (The -u option to GNU