mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-05 16:20:10 +00:00
92e632d525
Tell people about the GNOME Live! page which gives a more detailed outline on building the GTK+ stack with Visual C++.
73 lines
3.4 KiB
Plaintext
73 lines
3.4 KiB
Plaintext
Please do not compile this package (GTK+) in paths that contain
|
|
spaces in them-as strange problems may occur during compilation or during
|
|
the use of the library.
|
|
|
|
A more detailed outline for instructions on building the GTK+ with Visual
|
|
C++ can be found in the following GNOME Live! page:
|
|
|
|
https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack
|
|
|
|
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: GDK-Pixbuf, Pango,
|
|
ATK and GLib. External dependencies are at least Cairo, zlib, libpng,
|
|
gettext-runtime; and optional dependencies are fontconfig*, freetype*
|
|
and expat*. See the build/win32/vs10/README.txt file in glib for
|
|
details where to unpack them.
|
|
|
|
It is recommended that one builds the dependencies with VS9 as far as
|
|
possible, especially those from and using the GTK+ stack (i.e. GLib,
|
|
ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
|
|
to different CRTs can be kept at a minimum. zlib, libpng, and Cairo
|
|
do contain support for compiling under VS9 using VS
|
|
project files and/or makefiles at this time of writing, For the
|
|
GTK+ stack, VS9 project files are either available under
|
|
$(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK
|
|
(unstable) and GDK-Pixbuf (unstable), and should be in the next
|
|
unstable version of Pango. There is no known official VS9 build
|
|
support for fontconfig (along with freetype and expat) and
|
|
gettext-runtime, so please use the binaries from:
|
|
|
|
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
|
|
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
|
|
|
|
The recommended build order for these dependencies:
|
|
(first unzip any dependent binaries downloaded from the ftp.gnome.org
|
|
as described in the README.txt file in the build/win32/vs9 folder)
|
|
-zlib
|
|
-libpng
|
|
-(optional for GDK-Pixbuf) IJG JPEG
|
|
-(optional for GDK-Pixbuf) requires zlib and IJG JPEG)libtiff
|
|
-(optional for GDK-Pixbuf) jasper [jpeg-2000 library])
|
|
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to
|
|
build PCRE is recommended-see build/win32/vs9/README.txt of GLib)
|
|
-Cairo
|
|
-GLib
|
|
-ATK
|
|
-Pango
|
|
-GDK-Pixbuf
|
|
(note the last 3 dependencies are not interdependent, so the last 3
|
|
dependencies can be built in any order)
|
|
|
|
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.
|
|
|
|
*About the dependencies marked with *: These dependencies are not
|
|
compulsory components for building and running GTK+ itself, but note
|
|
that they are needed for people running and building GIMP.
|
|
They are referred to by components in Cairo and Pango mainly-so decide
|
|
whether you will need FontConfig/FreeType support prior to building
|
|
Cairo and Pango, which are hard requirements for building and running
|
|
GTK+.
|
|
--Tor Lillqvist <tml@iki.fi>
|
|
--Updated by Fan, Chun-wei <fanc999@yahoo.com.tw>
|