gtk2/build/win32/vs9
Chun-wei Fan e05cde5964 Update VS property sheet
Make GDK-Pixbuf include path more consitent with autofiscated builds
2011-03-26 11:49:53 +08:00
..
gdk-win32.vcproj Visual C++ support: Fix the gdk-win32 Project 2011-02-11 17:45:32 +08:00
gdk.vcprojin Update Visual C++ 2008 Project Files Stuff 2011-01-24 00:10:19 +08:00
gtk-demo.vcproj Update MSVC 2008 Project Files 2011-01-12 18:36:05 +08:00
gtk.vcprojin Update MSVC 2008 Project Files 2011-01-12 18:36:05 +08:00
gtk+.sln gtk+.sln: Remove GDK-Pixbuf compilation stuff 2010-11-13 15:23:32 +09:00
gtk+.vsprops Update VS property sheet 2011-03-26 11:49:53 +08:00
install.vcproj Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03:00
Makefile.am Remove no longer existing files 2010-11-13 15:23:33 +09:00
README.txt Update Visual C++ 2008 Project Files Stuff 2011-01-24 00:10:19 +08:00

Note that all this is rather experimental.

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 zlib, libpng,
proxy-libintl, fontconfig, freetype, expat.  See the corresponding
README.txt file in glib for details where to unpack them.

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-3.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.

--Tor Lillqvist <tml@iki.fi>
--Updated by Chun-wei Fan <fanc999 --at-- yahoo --dot-- com --dot-- tw>