mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-07 01:00:28 +00:00
e544602065
Similar setup as in GLib and Pango. Also here we use a build/win32/vs9 subfolder, even if there is nothing else in build or build/win32.
23 lines
1.1 KiB
Plaintext
23 lines
1.1 KiB
Plaintext
Note that all this is rather experimental.
|
|
|
|
This VS9 solution and the projects it includes are intented to be used
|
|
in a GTK+ 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 files needed, like config.h.win32.in into config.h.win32 and the
|
|
.vcprojin files here into corresponding actual .vcproj files.
|
|
|
|
You will need the parts from below in the GTK+ stack: pango, atk and
|
|
glib. External dependencies are at least zlib, libpng, proxy-libintl,
|
|
fontconfig, freetype, expat. See the corresponding README.txt file in
|
|
glib for details where to unpack them.
|
|
|
|
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 GTK+ headers into
|
|
<root>\vs9\<PlatformName>\include\gtk-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>
|