-Note that all this is rather experimental.
-
-This VS10 solution and the projects it includes are intented to be used
-in a GLib 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 .in files needed, mainly config.h.win32.in into config.h.win32 and
-glibconfig.h.win32.in into glibconfig.h.win32. You will also need to
-expand the .vcprojin files here into .vcproj files.
-
-The required dependencies are zlib and proxy-libintl. Fetch the latest
-proxy-libintl-dev and zlib-dev zipfiles from
-http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit
-builds, and correspondingly
-http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ for 64-bit
-builds.
-
-One may wish to build his/her own ZLib-It is recommended that ZLib is
-built using the win32/Makefile.msc makefile with VS10 with the ASM routines
-to avoid linking problems-see win32/Makefile.msc in ZLib for more details.
-
-One may optionally use his/her own PCRE installation by selecting the
-(BuildType)_ExtPCRE configuration, but please note the PCRE must be built
-with VS10 with unicode support using the /MD (release) or /MDd (debug)
-runtime option which corresponds to your GLib build flavour (release, debug).
-(These are the defaults set by CMAKE, which is used in recent versions of PCRE.)
-Not doing so will most probably result in unexpected crashes in
-your programs due to the use of different CRTs. If using a static PCRE
-build, add PCRE_STATIC to the "preprocessor definitions".
-Note that one may still continue to build with the bundled PCRE by selecting
-the (BuildType) configuration.
-
-Set up the source tree as follows under some arbitrary top
-folder <root>:
-
-<root>\<this-glib-source-tree>
-<root>\vs10\<PlatformName>
-
-*this* file you are now reading is thus located at
-<root>\<this-glib-source-tree>\build\win32\vs10\README.
-
-<PlatformName> is either Win32 or x64, as in VS10 project files.
-
-You should unpack the proxy-libintl-dev zip file into
-<root>\vs10\<PlatformName>, so that for instance libintl.h end up at
-<root>\vs10\<PlatformName>\include\libintl.h.
-
-The "install" project will copy build results and headers into their
-appropriate location under <root>\vs10\<PlatformName>. For instance,
-built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into
-<root>\vs10\<PlatformName>\lib and GLib headers into
-<root>\vs10\<PlatformName>\include\glib-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>
---Updated by Chun-wei Fan <fanc999@gmail.com>
+Note that all this is rather experimental.\r
+\r
+This VS10 solution and the projects it includes are intented to be used\r
+in a GLib source tree unpacked from a tarball. In a git checkout you\r
+first need to use some Unix-like environment or manual work to expand\r
+the .in files needed, mainly config.h.win32.in into config.h.win32 and\r
+glibconfig.h.win32.in into glibconfig.h.win32. You will also need to\r
+expand the .vcprojin files here into .vcproj files.\r
+\r
+The required dependencies are zlib, proxy-libintl and LibFFI. Fetch the latest\r
+proxy-libintl-dev and zlib-dev zipfiles from\r
+http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ for 32-bit\r
+builds, and correspondingly\r
+http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ for 64-bit\r
+builds.\r
+\r
+One may wish to build his/her own ZLib-It is recommended that ZLib is\r
+built using the win32/Makefile.msc makefile with VS10 with the ASM routines\r
+to avoid linking problems-see win32/Makefile.msc in ZLib for more details.\r
+\r
+For LibFFI, please get version 3.0.10rc8 or later, as Visual C++ build support\r
+was added in the 3.0.10(rc) release series. Please see the README file that\r
+comes with the LibFFI source package for more details on how to build LibFFI\r
+on Visual C++-please note that the mozilla-build package from Mozilla is needed\r
+in order to build LibFFI on Windows.\r
+\r
+One may optionally use his/her own PCRE installation by selecting the\r
+(BuildType)_ExtPCRE configuration, but please note the PCRE must be built\r
+with VS10 with unicode support using the /MD (release) or /MDd (debug)\r
+runtime option which corresponds to your GLib build flavour (release, debug).\r
+(These are the defaults set by CMAKE, which is used in recent versions of PCRE.)\r
+Not doing so will most probably result in unexpected crashes in \r
+your programs due to the use of different CRTs. If using a static PCRE\r
+build, add PCRE_STATIC to the "preprocessor definitions".\r
+Note that one may still continue to build with the bundled PCRE by selecting\r
+the (BuildType) configuration.\r
+\r
+Set up the source tree as follows under some arbitrary top\r
+folder <root>:\r
+\r
+<root>\<this-glib-source-tree>\r
+<root>\vs10\<PlatformName>\r
+\r
+*this* file you are now reading is thus located at\r
+<root>\<this-glib-source-tree>\build\win32\vs10\README.\r
+\r
+<PlatformName> is either Win32 or x64, as in VS10 project files.\r
+\r
+You should unpack the proxy-libintl-dev zip file into\r
+<root>\vs10\<PlatformName>, so that for instance libintl.h end up at\r
+<root>\vs10\<PlatformName>\include\libintl.h.\r
+\r
+For LibFFI, one should also put the generated ffi.h and ffitarget.h\r
+into <root>\vs10\<PlatformName>\include\ and the compiled static libffi.lib\r
+(or copy libffi-convenience.lib into libffi.lib) into \r
+<root>\vs10\<PlatformName>\lib\.\r
+\r
+The "install" project will copy build results and headers into their\r
+appropriate location under <root>\vs10\<PlatformName>. For instance,\r
+built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into\r
+<root>\vs10\<PlatformName>\lib and GLib headers into\r
+<root>\vs10\<PlatformName>\include\glib-2.0. This is then from where\r
+project files higher in the stack are supposed to look for them, not\r
+from a specific GLib source tree.\r
+\r
+--Tor Lillqvist <tml@iki.fi>\r
+--Updated by Chun-wei Fan <fanc999@gmail.com>\r
projects / platform / upstream / glib.git / commitdiff