gtk/build/win32/vs9
Chun-wei Fan 8f8da26c18 Update Visual C++ compilation items
-Added Visual C++ 2010 project files.  They are like the VS 2008 projects
 where the GDK and GTK+ projects are filled-in templates, which are filled-
 in during 'make dist', and added related README.txt file, and add them
 into distribution
-Updated the VS 2008 README.txt to reflect the latest situation regarding
 dependencies etc.
-Updated README.win32 to tell people about the now-available VS2010 projects
-Updated config.h.win32.in as VS 2010 ships with stdint.h
2011-07-25 12:20:21 +08:00
..
gdk-pixbuf-csource.vcproj Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03:00
gdk-pixbuf-query-loaders.vcproj Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03:00
gdk-pixbuf.vcproj Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03:00
gdk-win32.vcproj Update VS 2008 projects 2011-06-16 13:34:54 +08:00
gdk.vcprojin Update VS 2008 projects 2011-06-16 13:34:54 +08:00
gtk-demo.vcproj Update VS 2008 projects 2011-06-16 13:34:54 +08:00
gtk.vcprojin Update VS 2008 projects 2011-06-16 13:34:54 +08:00
gtk+.sln gtk+.sln: Remove all Gdk-Pixbuf compilation stuff for 2.24 2010-11-10 09:03:13 +08:00
gtk+.vsprops Update VS 2008 property sheet 2011-06-21 10:13:56 +08:00
install.vcproj Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03:00
Makefile.am Don't distribute GDK-Pixbuf VS 2008 Projects 2011-02-25 13:46:39 +08:00
README.txt Update Visual C++ compilation items 2011-07-25 12:20:21 +08:00

Note that all this is rather experimental.

Please do not compile GTK+ in a path that contains spaces, as this
may cause problems during the build and/or during the use of the
library.

This VS9 solution and the projects it includes are intented to be used
in a GTK+ source tree unpacked from a tarball. In a git checkout you
first need to use some Unix-like environment or manual work to expand
the files needed, like config.h.win32.in into config.h.win32 and the
.vcprojin files here into corresponding actual .vcproj files.

You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
ATK and GLib.  External dependencies are at least Cairo, zlib, libpng,
gettext-runtime; and optional dependencies  are fontconfig*, freetype*
and expat*.  See the build/win32/vs10/README.txt file in glib for
details where to unpack them.

It is recommended that one builds the dependencies with VS9 as far as
possible, especially those from and using the GTK+ stack (i.e. GLib,
ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
to different CRTs can be kept at a minimum.  zlib, libpng, and Cairo
do contain support for compiling under VS9 using VS
project files and/or makefiles at this time of writing, For the
GTK+ stack, VS9 project files are either available under
$(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK
(unstable) and GDK-Pixbuf (unstable), and should be in the next
unstable version of Pango.  There is no known official VS9 build
support for fontconfig (along with freetype and expat) and
gettext-runtime, so please use the binaries from: 

ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)

The recommended build order for these dependencies:
(first unzip any dependent binaries downloaded from the ftp.gnome.org
 as described in the README.txt file in the build/win32/vs9 folder)
-zlib
-libpng
-(optional for GDK-Pixbuf) IJG JPEG
-(optional for GDK-Pixbuf) requires zlib and IJG JPEG)libtiff
-(optional for GDK-Pixbuf) jasper [jpeg-2000 library])
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to
  build PCRE is recommended-see build/win32/vs9/README.txt of GLib)
-Cairo
-GLib
-ATK
-Pango
-GDK-Pixbuf
(note the last 3 dependencies are not interdependent, so the last 3
 dependencies can be built in any order)

The "install" project will copy build results and headers into their
appropriate location under <root>\vs9\<PlatformName>. For instance,
built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
<root>\vs9\<PlatformName>\lib and GTK+ headers into
<root>\vs9\<PlatformName>\include\gtk-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.

*About the dependencies marked with *: These dependencies are not
 compulsory components for building and running GTK+ itself, but note
 that they are needed for people running and building GIMP.
 They are referred to by components in Cairo and Pango mainly-so decide
 whether you will need FontConfig/FreeType support prior to building
 Cairo and Pango, which are hard requirements for building and running
 GTK+. 
--Tor Lillqvist <tml@iki.fi>
--Updated by Fan, Chun-wei <fanc999@yahoo.com.tw>