mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-11-10 19:36:18 +01:00
088b08bdfc
-Reinstate build/win32/vs10/glib.sln with the correct EOL (DOS/Windows) so that the file can be correctly recognized by Windows, rather than having the "Unrecognized Visual Studio Version". -Update the main GLib projects to output the DLL/LIB file into <Release or Debug>\<Win32 or x64>\bin for all configurations. -Update/simplify the property sheets to copy all DLL and LIB files from <Release or Debug>\<Win32 or x64>\bin for all configurations. -Update the VS 2008 property sheet to seperate the intermediate directories for all projects as well to avoid errors/warnings of being unable to write/access the PDB files as they are in use. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| gio.vcprojin | ||
| glib-compile-schemas.vcproj | ||
| glib-genmarshal.vcproj | ||
| glib.sln | ||
| glib.vcprojin | ||
| glib.vsprops | ||
| gmodule.vcproj | ||
| gobject.vcprojin | ||
| gsettings.vcproj | ||
| gspawn-win32-helper-console.vcproj | ||
| gspawn-win32-helper.vcproj | ||
| gthread.vcproj | ||
| install.vcproj | ||
| Makefile.am | ||
| README.txt | ||
| testglib.vcproj | ||
Note that all this is rather experimental. This VS9 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 VS9 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 VS9 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>\vs9\<PlatformName> *this* file you are now reading is thus located at <root>\<this-glib-source-tree>\build\win32\vs9\README. <PlatformName> is either Win32 or x64, as in VS9 project files. You should unpack the proxy-libintl-dev zip file into <root>\vs9\<PlatformName>, so that for instance libintl.h end up at <root>\vs9\<PlatformName>\include\libintl.h. 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 GLib headers into <root>\vs9\<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>