mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-06 16:50:11 +00:00
465005f929
Add some flexibility in the property sheets for one building GTK+ that it also searches for a settable installation path of Python, in addition to searching the PATH for an installation of the Python interpretor. This currently defaults to Python 2.7.x, which is normally installed in c:\python27 on Windows by default. Also tell people in the README.txt's for the Visual Studio builds
97 lines
4.7 KiB
Plaintext
97 lines
4.7 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 VS10 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
|
|
.vcxprojin and .vcxproj.filtersin files here into corresponding actual
|
|
.vcxproj and vcxproj.filters files.
|
|
|
|
You will need the parts from below in the GTK+ stack: GDK-Pixbuf, Pango,
|
|
ATK and GLib. External dependencies are at least Cairo
|
|
(with Cairo-GObject support, meaning Cairo 1.10.x or later), zlib, libpng,
|
|
gettext-runtime, fontconfig*, freetype*, expat*. See the
|
|
build/win32/vs10/README.txt file in glib for details where to unpack them.
|
|
|
|
You will also need a Python 2.6+/3.x interpretor installed on your system,
|
|
which can be obtained from the official installers available from
|
|
http://www.python.org. Please note that the Python interpretor (python.exe)
|
|
either needs to be in your PATH before attempting the build of GTK+, or it
|
|
can be found in the path specified by PythonPath in gtk-version-paths.props.
|
|
If you happen to change the PythonPath setting in gtk-version-paths.props after
|
|
opening gtk+.sln with Visual Studio, you will need to close the gtk+.sln solution,
|
|
delete all the *.sdf, *.suo and *.user files before re-attempting the build.
|
|
|
|
It is recommended that one builds the dependencies with VS10 as far as
|
|
possible, especially those from and using the GTK+ stack (i.e. GLib,
|
|
Cairo, 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 VS10
|
|
using VS project files and/or makefiles at this time of writing, For the
|
|
GTK+ stack, VS10 project files are either available under
|
|
$(srcroot)/build/vs10 in the case of GLib (stable/unstable), ATK
|
|
(stable/unstable) and GDK-Pixbuf (unstable), and should be in the next
|
|
unstable version of Pango. There is no known official VS10 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)
|
|
|
|
Unzip the binaries obtained from ftp.gnome.org in <root>\vs10\<PlatformName>,
|
|
and build the following, if not already done so:
|
|
|
|
Note: put the resulting zlib, libpng, pcre and Cairo files as follows:
|
|
.dll files: <root>\vs10\<PlatformName>\bin
|
|
.lib files: <root>\vs10\<PlatformName>\lib
|
|
.h files: <root>\vs10\<PlatformName>\include
|
|
|
|
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/vs10 folder)
|
|
-zlib
|
|
-libpng
|
|
-(for GDK-Pixbuf, if not using GDI+) IJG JPEG
|
|
-(for GDK-Pixbuf, if not using GDI+) libtiff
|
|
[libtiff requires zlib and IJG JPEG]
|
|
-(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library]
|
|
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to
|
|
build PCRE is recommended-see build/win32/vs10/README.txt of GLib)
|
|
-GLib **
|
|
-Cairo (inclusive of Cairo-GObject)
|
|
-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>\vs10\<PlatformName>. For instance,
|
|
built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into
|
|
<root>\vs10\<PlatformName>\lib and GTK+ headers into
|
|
<root>\vs10\<PlatformName>\include\gtk-3.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 optional
|
|
as those are not compulsory components for building and running GTK+
|
|
itself, but note that they are needed for people running and building
|
|
GIMP or those who need complex script support via fontconfig. They
|
|
are referred to by components in Cairo and Pango mainly.
|
|
Decide whether you need fontconfig support prior to building Cairo
|
|
and Pango.
|
|
|
|
**:Put the sources of the packages marked with ** in <root>\<package-
|
|
source-tree>, and build with VS10 from there.
|
|
|
|
--Tor Lillqvist <tml@iki.fi>
|
|
--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>
|