mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-02 19:06:16 +01:00
cd23ae7134
These are the actual GLib VS2010 project files (*.vcxproj, *.vcxproj.filters) and property sheet file (*.props) that are used to compile the GLib, GModule, GObject, GThread, GIO DLLs, along with the gspawn-win32-helper* programs, glib-genmarshal utility and testglib test program. A readme.txt file is also enclosed for references for building GLib under VS2010. Note that the project files for GLib, GIO and GObject are templates that makes use of the autotools items of my last commit so that maintenance of those files are simplified as new source files are added to these rather frequently. Suggestions are welcome for these-please let me know via BugZilla. Thank you!
53 lines
2.4 KiB
Plaintext
53 lines
2.4 KiB
Plaintext
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 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>\glib\<this-glib-source-tree>
|
|
<root>\vs10\<PlatformName>
|
|
|
|
*this* file you are now reading is thus located at
|
|
<root>\glib\<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>
|