mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-11-10 19:00:08 +00:00
Update build/win32/vs9/README.txt
Make the VS 2008 build instructions and information more up-to-date and clearer to people. Please let me know if I have missed any needed details... Thanks
This commit is contained in:
parent
1ad1c33f52
commit
11ba5c209b
@ -6,10 +6,45 @@ 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 zlib, libpng,
|
||||
proxy-libintl, fontconfig, freetype, expat. See the corresponding
|
||||
README.txt file in glib for details where to unpack them.
|
||||
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/vs9/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,
|
||||
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 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)
|
||||
-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>\vs9\<PlatformName>. For instance,
|
||||
@ -19,5 +54,12 @@ built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
|
||||
project files higher in the stack are supposed to look for them, not
|
||||
from a specific GLib source tree.
|
||||
|
||||
*About the dependencies marked with *: I will see whether it is possible
|
||||
to reduce the depepdencies on building and running GTK+ by making these
|
||||
dependencies 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. They are referred to by components
|
||||
in Cairo and Pango mainly.
|
||||
|
||||
--Tor Lillqvist <tml@iki.fi>
|
||||
--Updated by Chun-wei Fan <fanc999 --at-- yahoo --dot-- com --dot-- tw>
|
||||
--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>
|
||||
|
Loading…
Reference in New Issue
Block a user