gtk/build/win32/vs9
Chun-wei Fan f79266092b Update MSVC 2008 Project Files
-Update the project files to simplify them a bit after the seperation of
 GDK-Pixbuf (move GDK-Pixbuf includes into the property sheet, move the
 linking of Cairo/Pango/PangoCairo into the property sheet)--this is for
 all DLL/EXE Projects (GDK/GTK/gtk-demo)

-Update the GDK-Win32 project as the source files have changed
 significantly (especially as GDK3 was not compilable on Windows for a
 while--thanks to Hans Breuer for the help in the process-Bug 639127)

-Made up for missed headers in the "install" stage and removed the removed
 headers in the property sheet

-Updated GTK+ .def file generation as an extra macro is needed for that

-Updated gdk/Makefile.am for the generation of gdk.vcproj from gdk.vcprojin
2011-01-12 18:36:05 +08:00
..
gdk-win32.vcproj Update MSVC 2008 Project Files 2011-01-12 18:36:05 +08:00
gdk.vcprojin Update MSVC 2008 Project Files 2011-01-12 18:36:05 +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 MSVC 2008 Project Files 2011-01-12 18:32:57 +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 Add Visual Studio 2008 project files 2010-04-12 12:45:40 +03: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: 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-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.

--Tor Lillqvist <tml@iki.fi>