Please do not compile this package (GLib) in paths that contain

spaces in them-as strange problems may occur during compilation or during

the use of the library.

Please refer to the following GNOME Live! page for more detailed

instructions on building GLib and its dependencies with Visual C++:

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

This VS11 solution and the projects it includes are intented to be used

in a GLib source tree unpacked from a tarball. In a git checkout you

first need to use some Unix-like environment or run build/win32/setup.py, 

which will do the work for you:

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

for more usage on this script, run

$python build/win32/setup.py -h/--help

The required dependencies are zlib, proxy-libintl and LibFFI. Fetch the latest

proxy-libintl-dev and zlib-dev zipfiles from

http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit

builds, and correspondingly

http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ for 64-bit

builds.

A Python 2.7.x or 3.x interpreter is also required, in order to generate

the utility scripts, as well as the pkg-config files for the build.  Please

see the entry "PythonDir" in glib-version-paths.props to verify that

it is correct.

One may wish to build his/her own ZLib-It is recommended that ZLib is

built using the win32/Makefile.msc makefile with VS11 with the ASM routines

to avoid linking problems-see win32/Makefile.msc in ZLib for more details.

For LibFFI, please use the Centricular fork of it, which can be found at

https://github.com/centricular/libffi.  Please refer to the instructions

there on building, as it involves using the Meson build system and possibly

the Ninja build tool if the Visual Studio project generation is not used

or is unavailable.

Please note, although using one's own existing PCRE installation to build GLib

is possible, it is still recommended to build PCRE during the process of building

GLib (i.e. using the Debug or Release configurations), as GLib's bundled PCRE

has been patched to work optimally with GLib.  If building against an existing

PCRE is desired, use the(BuildType)_ExtPCRE configurations, but one needs to ensure

that the existing PCRE is:

-Built with VS11

-Unicode support is built in (please see the CMake options for this)

-It is built with the Multithreaded DLL (/MD, for release builds) or the

 Multithreaded DLL Debug (/MDd, for debug builds)

If using static builds of PCRE, please add PCRE_STATIC to the "Preprocessor

Definitions" of the glib project settings.

Please be aware that the GLib's regex test program will only pass with PCRE directly

built into GLib.

Set up the source tree as follows under some arbitrary top

folder <root>:

<root>\<this-glib-source-tree>

<root>\vs11\<PlatformName>

*this* file you are now reading is thus located at

<root>\<this-glib-source-tree>\build\win32\vs11\README.

<PlatformName> is either Win32 or x64, as in VS11 project files.

You should unpack the proxy-libintl-dev zip file into

<root>\vs11\<PlatformName>, so that for instance libintl.h end up at

<root>\vs11\<PlatformName>\include\libintl.h.

For LibFFI, one should also put the generated ffi.h and ffitarget.h

into <root>\vs11\<PlatformName>\include\ and the compiled static libffi.lib

(or copy libffi-convenience.lib into libffi.lib) into 

<root>\vs11\<PlatformName>\lib\.

The "install" project will copy build results and headers into their

appropriate location under <root>\vs11\<PlatformName>. For instance,

built DLLs go into <root>\vs11\<PlatformName>\bin, built LIBs into

<root>\vs11\<PlatformName>\lib and GLib headers into

<root>\vs11\<PlatformName>\include\glib-2.0. This is then from where

project files higher in the stack are supposed to look for them, not

from a specific GLib source tree.

Note: If you see C4819 errors and you are compiling GLib on a DBCS

(Chinese/Korean/Japanese) version of Windows, you may need to switch

to an English locale in Control Panel->Region and Languages->System->

Change System Locale, reboot and rebuild to ensure GLib, Pango, GDK-Pixbuf,

ATK and GTK+ is built correctly.  This is due to a bug in Visual C++ running

on DBCS locales, and also affects many other opensource projects which are

built with Visual C++, including but not limited to QT and the Mozilla apps.

--Tor Lillqvist <tml@iki.fi>

--Updated by Chun-wei Fan <fanc999@gmail.com>