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, 11 insertions, 0 deletions

diff --git a/pango/module-defs-lang.c.win32 b/pango/module-defs-lang.c.win32
new file mode 100644
index 00000000..d1fe979d
--- /dev/null
+++ b/pango/module-defs-lang.c.win32
@@ -0,0 +1,11 @@
+/* Autogenerated and saved for builds using Microsoft's compiler,
+ * when the configure mechanism isn't used.
+ */
+
+#include "module-defs.h"
+
+PangoIncludedModule _pango_included_lang_modules[] = {
+ { _pango_arabic_lang_script_engine_list, _pango_arabic_lang_script_engine_init, _pango_arabic_lang_script_engine_exit, _pango_arabic_lang_script_engine_create },
+ { _pango_indic_lang_script_engine_list, _pango_indic_lang_script_engine_init, _pango_indic_lang_script_engine_exit, _pango_indic_lang_script_engine_create },
+ { NULL, NULL, NULL, NULL },
+};