Low-level core library that forms the basis for projects such as GTK+ and GNOME.
Go to file
Philip Withnall c26aab36db gio: Fix a minor indentation problem
Signed-off-by: Philip Withnall <withnall@endlessm.com>
Reviewed-by: nobody
2017-12-04 10:38:01 +00:00
build build: Drop nmake/MSC build system for GLib 2017-07-10 11:22:40 +01:00
docs Remove outdated/obsolete README 2017-11-27 12:55:34 +00:00
gio gio: Fix a minor indentation problem 2017-12-04 10:38:01 +00:00
glib gvariant: Clarify return docs for g_variant_get_normal_form() 2017-12-03 20:01:39 +00:00
gmodule GModule win32: disable error dialog popup 2017-11-02 15:34:14 +00:00
gobject gobject: Minor typo fix in a g_critical() warning 2017-11-29 17:51:19 +00:00
gthread meson: add -fvisibility=hidden explicitly to selected targets 2017-07-13 19:03:39 -04:00
m4macros build: Add #serial lines to m4 files 2017-10-26 12:26:14 +01:00
po Updated Hebrew translation 2017-11-26 15:46:05 +02:00
subprojects Add zlib, libffi, and proxy-libintl subproject wraps 2017-07-13 19:03:39 -04:00
tests tests: Work around a gdb bug in assert-msg-test 2017-11-27 11:44:08 +00:00
win32 Visual Studio 2008 Projects: Improve binary security 2017-10-20 16:44:21 +08:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.gitattributes git: Add .gitattributes file with EOL settings for README.win32 2017-07-10 11:35:31 +01:00
.gitignore Add zlib, libffi, and proxy-libintl subproject wraps 2017-07-13 19:03:39 -04:00
acglib.m4 Update GLIB_CHECK_COMPILE_WARNINGS macro to work with Autoconf 2.64 2009-08-14 21:36:42 +02:00
acinclude.m4 Move some inter-*.m4 includes from configure.in to acinclude.m4 to avoid 2007-11-08 02:43:17 +00:00
AUTHORS Updates 2005-12-26 05:23:08 +00:00
autogen.sh Fix problems with CLEANFILES and automake-1.11.1 2012-08-17 13:41:34 -04:00
ChangeLog.pre-1-2 Fix typos: invokation -> invocation. 2005-08-10 10:46:55 +00:00
ChangeLog.pre-2-0 Fix typos: invokation -> invocation. 2005-08-10 10:46:55 +00:00
ChangeLog.pre-2-2 Split ChangeLog 2002-12-28 21:16:55 +00:00
ChangeLog.pre-2-4 Move aside ChangeLog for 2.4 2004-05-04 20:13:47 +00:00
ChangeLog.pre-2-6 Split ChangeLog for 2.6 2005-01-10 15:52:23 +00:00
ChangeLog.pre-2-8 Truncate ChangeLog after moving aside 2005-08-24 18:53:51 +00:00
ChangeLog.pre-2-10 Adjust docs 2006-03-23 13:38:17 +00:00
ChangeLog.pre-2-12 Branch for 2.12 2006-08-23 03:43:36 +00:00
ChangeLog.pre-2-14 Added missing ChangeLog 2007-11-08 11:11:39 +00:00
ChangeLog.pre-2-16 Rotate ChangeLog 2008-03-12 16:13:54 +00:00
ChangeLog.pre-2-18 Bump version to 2.19.0 2008-09-18 14:47:14 +00:00
ChangeLog.pre-2-20 Rename ChangeLog to ChangeLog.pre-2-20 2009-04-02 23:14:54 -04:00
check-abis.sh check-abis.sh: allow _ftext as that's leaked on mips 2013-04-16 15:44:27 +02:00
config.h.meson meson: Fix libmount support 2017-10-31 15:24:04 +00:00
config.h.win32.in config.h.win32.in: Fix previous commit 2017-09-15 11:48:58 +08:00
configure.ac build: Include $host_cpu in tapset directory 2017-11-28 14:00:26 +00:00
COPYING Update COPYING file to LGPLv2.1 2017-05-29 19:53:35 +02:00
gio-2.0.pc.in gio-2.0.pc: include libmount in Libs.private 2016-11-22 13:06:36 -05:00
gio-unix-2.0.pc.in gio: Move gmodule to Requires.private 2011-11-22 13:59:34 -05:00
gio-windows-2.0.pc.in Add GWin32InputStream and GWin32OutputStream classes 2010-04-19 11:54:56 +03:00
glib-2.0.pc.in build: Include Cocoa/Carbon in Libs.private if targetting Mac OS X 2014-04-01 19:11:32 +01:00
glib-gettextize.in meson: Fix permissions of installed scripts 2017-10-11 09:49:26 +01:00
glib-tap.mk glib-tap: Add missing mkdir for .test generation rule 2017-11-24 13:10:11 +00:00
glib-zip.in Add gdbus-codegen to glib-zip.in 2011-08-25 17:23:00 -04:00
glib.doap Update maintainer record in DOAP 2016-02-18 12:15:35 -05:00
glib.mk build: fix 'make distclean' 2014-01-13 16:43:12 -05:00
glib.supp valgrind: Add false positive to suppressions file 2017-09-08 15:36:32 +01:00
gmodule-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config 2009-11-17 20:41:48 -06:00
gmodule-export-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config 2009-11-17 20:41:48 -06:00
gmodule-no-export-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config 2009-11-17 20:41:48 -06:00
gobject-2.0.pc.in gobject.pc: remove dependency on gthread 2011-10-16 19:17:52 -04:00
gthread-2.0.pc.in Default to --disable-gtk-doc, to avoid Jade setup hassles. 2002-03-05 05:18:23 +00:00
HACKING docs: Add a README.rationale documenting major design decisions 2014-05-04 18:22:09 +01:00
INSTALL.in Update URLs library.gnome.org -> developer.gnome.org 2014-09-18 20:32:43 +02:00
Makefile.am build: Use AM_DISTCHECK_CONFIGURE_FLAGS rather than unprefixed version 2017-11-23 16:37:00 +00:00
meson_options.txt meson: Add 'charsetalias-dir' option mirroring the autotools one 2017-11-22 04:43:05 +05:30
meson.build build: Include host_machine.cpu_family() in tapset directory (Meson) 2017-11-28 15:07:47 +00:00
msvc_recommended_pragmas.h msvc_recommended_pragmas.h: Treat C4819 warnings as errors 2013-11-25 15:26:25 +08:00
NEWS 2.55.0 2017-11-15 22:00:19 -05:00
NEWS.pre-1-3 updates. 2001-04-03 19:22:44 +00:00
README.commits Update README files to refer to git 2009-03-31 19:39:16 -04:00
README.in Use system PCRE unless --with-pcre=internal is given 2016-01-14 13:09:06 +00:00
README.rationale docs: Add a README.rationale documenting major design decisions 2014-05-04 18:22:09 +01:00
README.win32 Re-normalise line endings of README.win32 2017-07-10 11:37:30 +01:00
sanity_check Replace bash-specific == with sh-understood =. Fixes bug #373864. 2006-11-14 18:23:48 +00:00
tap-driver.sh Fix "on on" typo in tap-driver.sh comment 2017-11-16 11:16:28 +00:00
tap-test Start using TAP 2013-08-17 17:25:58 -04:00

Tor Lillqvist <tml@iki.fi>
Hans Breuer <hans@breuer.org>

Note that this document is not really maintained in a serious
fashion. Lots of information here might be misleading or outdated. You
have been warned.

The general parts, and the section about gcc and autoconfiscated
build, and about a Visual Studio build are by Tor Lillqvist.

General
=======

For prebuilt binaries (DLLs and EXEs) and developer packages (headers,
import libraries) of GLib, Pango, GTK+ etc for Windows, go to
http://www.gtk.org/download-windows.html . They are for "native"
Windows meaning they use the Win32 API and Microsoft C runtime library
only. No POSIX (Unix) emulation layer like Cygwin in involved.

To build GLib on Win32, you can use either gcc ("mingw") or the
Microsoft compiler and tools. For the latter, MSVC6 and later have
been used successfully. Also the Digital Mars C/C++ compiler has
reportedly been used.

You can also cross-compile GLib for Windows from Linux using the
cross-compiling mingw packages for your distro.

Note that to just *use* GLib on Windows, there is no need to build it
yourself.

On Windows setting up a correct build environment can be quite a task,
especially if you are used to just type "./configure; make" on Linux,
and expect things to work as smoothly on Windows.

The following preprocessor macros are to be used for conditional
compilation related to Win32 in GLib-using code:

- G_OS_WIN32 is defined when compiling for native Win32, without
  any POSIX emulation, other than to the extent provided by the
  bundled Microsoft C library (msvcr*.dll).

- G_WITH_CYGWIN is defined if compiling for the Cygwin
  environment. Note that G_OS_WIN32 is *not* defined in that case, as
  Cygwin is supposed to behave like Unix. G_OS_UNIX *is* defined by a GLib
  for Cygwin.

- G_PLATFORM_WIN32 is defined when either G_OS_WIN32 or G_WITH_CYGWIN
  is defined.

These macros are defined in glibconfig.h, and are thus available in
all source files that include <glib.h>.

Additionally, there are the compiler-specific macros:
- __GNUC__ is defined when using gcc
- _MSC_VER is defined when using the Microsoft compiler
- __DMC__ is defined when using the Digital Mars C/C++ compiler

G_OS_WIN32 implies using the Microsoft C runtime, normally
msvcrt.dll. GLib is not known to work with the older crtdll.dll
runtime, or the static Microsoft C runtime libraries libc.lib and
libcmt.lib. It apparently does work with the debugging version of
msvcrt.dll, msvcrtd.dll. If compiled with Microsoft compilers newer
than MSVC6, it also works with their compiler-specific runtimes, like
msvcr70.dll or msvcr80.dll. Please note that it's non totally clear if
you would be allowed by the license to distrubute a GLib linked to
msvcr70.dll or msvcr80.dll, as those are not part of the operating
system, but of the MSVC product. msvcrt.dll is part of Windows.

For people using Visual Studio 2005 or later:

If you are building GLib-based libraries or applications, or GLib itself
and you see a C4819 error (or warning, before C4819 is treated as an error
in msvc_recommended_pragmas.h), please be advised that this error/warning should
not be disregarded, as this likely means portions of the build is not being
done correctly, as this is an issue of Visual Studio running on CJK (East Asian)
locales.  This is an issue that also affects builds of other projects, such as
QT, Firefox, LibreOffice/OpenOffice, Pango and GTK+, along with many other projects.

To overcome this problem, please set your system's locale setting for non-Unicode to
English (United States), reboot, and restart the build, and the code should build
normally.  See also this GNOME Wiki page [1] that gives a bit further info on this.

Building software that use GLib or GTK+
=======================================

Building software that just *uses* GLib or GTK+ also require to have
the right compiler set up the right way. If you intend to use gcc,
follow the relevant instructions below in that case, too.

Tor uses gcc with the -mms-bitfields flag which means that in order to
use the prebuilt DLLs (especially of GTK+), if you compile your code
with gcc, you *must* also use that flag. This flag means that the
struct layout rules are identical to those used by MSVC. This is
essential if the same DLLs are to be usable both from gcc- and
MSVC-compiled code. Such compatibility is desirable.

When using the prebuilt GLib DLLs that use msvcrt.dll from code that
uses other C runtimes like for example msvcr70.dll, one should note
that one cannot use such GLib API that take or returns file
descriptors. On Windows, a file descriptor (the small integer as
returned by open() and handled by related functions, and included in
the FILE struct) is an index into a table local to the C runtime
DLL. A file descriptor in one C runtime DLL does not have the same
meaning in another C runtime DLL.

Building GLib
=============

Again, first decide whether you really want to do this.

Before building GLib you must also have a GNU gettext-runtime
developer package. Get prebuilt binaries of gettext-runtime from
http://www.gtk.org/download-windows.html .

Autoconfiscated build (with gcc)
================================

Tor uses gcc 3.4.5 and the rest of the mingw utilities, including MSYS
from www.mingw.org. Somewhat earlier or later versions of gcc
presumably also work fine.

Using Cygwin's gcc with the -mno-cygwin switch is not recommended. In
theory it should work, but Tor hasn't tested that lately. It can
easily lead to confusing situations where one mixes headers for Cygwin
from /usr/include with the headers for native software one really
should use. Ditto for libraries.

If you want to use mingw's gcc, install gcc, win32api, binutils and
MSYS from www.mingw.org.

Tor invokes configure using:

CC='gcc -mtune=pentium3 -mthreads' CPPFLAGS='-I/opt/gnu/include' \
	LDFLAGS='-L/opt/gnu/lib -Wl,--enable-auto-image-base' CFLAGS=-O2 \
	./configure --disable-gtk-doc --prefix=$TARGET

The /opt/gnu mentioned contains the header files for GNU and (import)
libraries for GNU libintl. The build scripts used to produce the
prebuilt binaries are included in the "dev" packages.

Please note that the ./configure mechanism should not blindly be used
to build a GLib to be distributed to other developers because it
produces a compiler-dependent glibconfig.h. For instance, the typedef
for gint64 is long long with gcc, but __int64 with MSVC.

Except for this and a few other minor issues, there shouldn't be any
reason to distribute separate GLib headers and DLLs for gcc and MSVC6
users, as the compilers generate code that uses the same C runtime
library.

The DLL generated by either compiler is binary compatible with the
other one. Thus one either has to manually edit glibconfig.h
afterwards, or use the supplied glibconfig.h.win32 which has been
produced by running configure twice, once using gcc and once using
MSVC, and merging the resulting files with diff -D.

For MSVC7 and later (Visual C++ .NET 2003, Visual C++ 2005, Visual C++
2008 etc) it is preferred to use specific builds of GLib DLLs that use
the same C runtime as the code that uses GLib. Such DLLs should be
named differently than the ones that use msvcrt.dll.

For GLib, the DLL that uses msvcrt.dll is called libglib-2.0-0.dll,
and the import libraries libglib-2.0.dll.a and glib-2.0.lib. Note that
the "2.0" is part of the "basename" of the library, it is not
something that libtool has added. The -0 suffix is added by libtool
and is the value of "LT_CURRENT - LT_AGE". The 0 should *not* be
thought to be part of the version number of GLib. The LT_CURRENT -
LT_AGE value will on purpose be kept as zero as long as binary
compatibility is maintained. For the gory details, see configure.ac
and libtool documentation.

Building with Visual Studio
===========================

A more detailed outline of building GLib with its dependencies can
now be found on the GNOME wiki:

https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack

Please do not build GLib in paths that contain spaces in them, as
this may cause problems during compilation and during usage of the
library.

In an unpacked tarball, you will find in build\win32\vs9 (VS 2008) and
build\win32\vs10 (VS 2010) a solution file that can be used to build
the GLib DLLs and some auxiliary programs under VS 2008 and VS 2010
(Express Edition will suffice with the needed dependencies) respectively.
Read the README.txt file in those folders for more
information. Note that you will need a libintl implementation, zlib, and 
libFFI.

If you are building from a GIT checkout, you will first need to use some
Unix-like environment or run win32/setup.py, 
which will expand the VS 2008/2010 project files, the DLL resouce files and
other miscellanious files required for the build.  Run win32/setup.py
as follows:

$python win32/setup.py --perl path_to_your_perl.exe

for more usage on this script, run
$python win32/setup.py -h/--help

[1]: https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack under "Preparations"