1 Note that all this is rather experimental.
\r
3 This VS9 solution and the projects it includes are intented to be used
\r
4 in a GLib source tree unpacked from a tarball. In a git checkout you
\r
5 first need to use some Unix-like environment or manual work to expand
\r
6 the .in files needed, mainly config.h.win32.in into config.h.win32 and
\r
7 glibconfig.h.win32.in into glibconfig.h.win32.
\r
9 The only external dependency is proxy-libintl. Fetch the latest
\r
10 proxy-libintl-dev zipfile from
\r
11 http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit
\r
12 builds, and correspondingly
\r
13 http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ for 64-bit
\r
14 builds. Set up the source tree as follows under some arbitrary top
\r
17 <root>\glib\<this-glib-source-tree>
\r
18 <root>\vs9\<PlatformName>
\r
20 *this* file you are now reading is thus located at
\r
21 <root>\glib\<this-glib-source-tree>\build\win32\vs9\README.
\r
23 <PlatformName> is either Win32 or x64, as in VS9 project files.
\r
25 You should unpack the proxy-libintl-dev zip file into
\r
26 <root>\vs9\<PlatformName>, so that for instance libintl.h end up at
\r
27 <root>\vs9\<PlatformName>\include\libintl.h.
\r
29 The "install" project will copy build results and headers into their
\r
30 appropriate location under <root>\vs9\<PlatformName>. For instance,
\r
31 built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
\r
32 <root>\vs9\<PlatformName>\lib and GLib headers into
\r
33 <root>\vs9\<PlatformName>\include\glib-2.0. This is then from where
\r
34 project files higher in the stack are supposed to look for them, not
\r
35 from a specific GLib source tree.
\r
37 --Tor Lillqvist <tml@iki.fi>
\r