Add solution and project files for Visual Studio builds

The VS files are kept in build/win32/vs9, the same relative location
as in GLib, mostly for historical reasons.

Update README.win32 to reflect the VS possibility.

Include the VS solution and project files in the tarball when doing a
release.

To avoid having to list source files in several locations, generate
files listing source files at "make dist" time in the corresponding
source directories. Use the C preprocessor to preprocess .vcprojin
files that include said list files into the actual .vcproj project
files.

Provide a rc file for the pangocairo DLL, too.

Construct and provide in the tarball a pregenerated config.h.win32
which can be used as config.h when building with Visual C without
running any configure script. Provide pregenerarated
module-defs.h.win32, module-defs-lang.c.win32 files too.

Define PANGO_MODULE_PREFIX appropriately in the relevant module source
files if not available from the compilation command line.

Update module-defs-fc.c.win32 and module-defs-win32.c.win32 to match
what the configure script provides.

1 files changed, 6 insertions, 22 deletions

diff --git a/README.win32 b/README.win32
index 68fcd8ab..283b6cb8 100644
--- a/README.win32
+++ b/README.win32
@@ -6,11 +6,11 @@ pangowin32). Much of the GDI font API calls are in cairo.
 The pangoft2 backend was originally written with Win32 in mind, but
 its main use nowadays is on other platforms than Win32.
 
-There are two ways to build Pango for Win32:
+There are three ways to build Pango for Win32:
 
 1) Use gcc (mingw), libtool, make, like on Unix.
 
-If building from CVS, run the autogen.sh script that runs aclocal,
+If building from git, run the autogen.sh script that runs aclocal,
 automake, autoconf and configure to build makefiles etc. This is what
 tml@novell.com uses. Pass the same switches to autogen.sh that you
 would pass to the configure script.
@@ -20,31 +20,15 @@ make should be enough. But, as always, you need to understand what is
 happening and follow the progress in case manual intervention is
 needed.
 
-If you want to support complex scripts (which you should!), you need
-the usp10.h header from the Platform SDK. Otherwise the basic-win32
-shaper module won' use Uniscribe and for instance Arabic and Indic
-scripts will look like crap. (Yes, complex script support *is*
-important. It is one of the main selling points of GTK+ and Pango.)
-Pass the --with-usp10 flag to the configure script to tell it where
-you have the Platform SDK (or other source of an "usp10.h" or
-"include/usp10.h" file).
-
 tml ran the configure script like this when building binaries for
 Pango 1.10.0:
 
-PATH=/devel/dist/glib-2.8.0/bin:$PATH ACLOCAL_FLAGS="-I /devel/dist/glib-2.8.0/share/aclocal" PKG_CONFIG_PATH=/devel/dist/glib-2.8.0/lib/pkgconfig:$PKG_CONFIG_PATH CC='gcc -mtune=pentium3' CPPFLAGS='-I/opt/gnu/include' LDFLAGS='-L/opt/gnu/lib' CFLAGS=-O ./configure --disable-gtk-doc --with-usp10=/opt/psdk  --without-x --prefix=c:/devel/target/pango-1.10.0
-
-The pango.modules file tends not to get automatically set up correctly
-on Win32. Check that. Also make sure you set up a pango.aliases file
-if you want to support non-Latin scripts. pango.aliases file used by
-tml looks like this:
+PATH=/devel/dist/glib-2.8.0/bin:$PATH ACLOCAL_FLAGS="-I /devel/dist/glib-2.8.0/share/aclocal" PKG_CONFIG_PATH=/devel/dist/glib-2.8.0/lib/pkgconfig:$PKG_CONFIG_PATH CC='gcc -mtune=pentium3' CPPFLAGS='-I/opt/gnu/include' LDFLAGS='-L/opt/gnu/lib' CFLAGS=-O ./configure --disable-gtk-doc  --without-x --prefix=c:/devel/target/pango-1.10.0
 
-tahoma = "tahoma,browallia new,mingliu,simhei,gulimche,ms gothic,latha,mangal"
-sans = "arial,browallia new,mingliu,simhei,gulimche,ms gothic,latha,mangal"
-serif = "times new roman,angsana new,mingliu,simsun,gulimche,ms gothic,latha,mangal"
-monospace = "courier new,courier monothai,mingliu,simsun,gulimche,ms gothic,latha,mangal"
+2) Use Visual Studio 2008. Use the solution file in
+build/win32/vs9. See the README.txt there for more information.
 
-2) Use MSVC and nmake. Use the makefile.msc makefiles. These makefiles
+3) Use MSVC and nmake. Use the makefile.msc makefiles. These makefiles
 are supported by Hans Breuer. They requires manual editing. You need
 to have the source code to some suitable version of glib in a sibling
 directory. Ask Hans for advice.