1 Note that all this is rather experimental.
\r
3 A more detailed description on using Visual C++ to compile COGL with
\r
4 its dependencies can be found on the following GNOME Live! page:
\r
6 https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack
\r
8 Please do not attempt to compile COGL in a path that contains spaces
\r
9 to avoid potential problems during compilation, linking or usage.
\r
11 This VS10 solution and the projects it includes are intented to be used
\r
12 in a Cogl source tree unpacked from a tarball. In a git checkout you
\r
13 first need to use some Unix-like environment or manual work to expand
\r
14 the files needed, like config.h.win32.in into config.h.win32 and the
\r
15 .vcprojin files here into corresponding actual .vcproj files.
\r
17 You will need the parts from GNOME: GDK-Pixbuf, Pango* and GLib.
\r
18 External dependencies are at least zlib, libpng,
\r
19 gettext-runtime* and Cairo*, and glext.h from
\r
20 http://www.opengl.org/registry/api/glext.h (which need to be in the GL folder
\r
21 in your include directories or in <root>\vs10\<PlatformName>\include\GL).
\r
23 Please see the README file in the root directory of this Cogl source package
\r
24 for the versions of the dependencies required. See also
\r
25 build/win32/vs10/README.txt in the GLib source package for details
\r
26 where to unpack them. It is recommended that at least the dependencies
\r
27 from GNOME are also built with VS10 to avoid crashes caused by mixing different
\r
28 CRTs-please see also the build/win32/vs10/README.txt in those respective packages.
\r
30 If building the SDL winsys is desired, you will also need the SDL libraries
\r
31 from www.libsdl.org-building the SDL source package with Visual C++ 2010
\r
32 is recommended (working Visual C++ 2005 projects are included with it, upgrade
\r
33 the projects one prompted), but one may want to use the VC8 binary packages
\r
36 The recommended build sequence of the dependencies are as follows (the non-GNOME
\r
37 packages that are not downloaded as binaries from ftp://ftp.gnome.org have
\r
38 makefiles and/or VS project files that can be used to compile with VS directly,
\r
39 except the optional PCRE, which is built on VS using CMake; GLib has
\r
40 VS10 project files in the latest stable versions, GDK-Pixbuf have VS10 project files
\r
41 in the latest unstable version, and Pango should have VS10 project files
\r
42 in the next unstable release):
\r
43 -Unzip the binary packages for gettext-runtime, freetype, expat and fontconfig
\r
44 downloaded from ftp://ftp.gnome.org*
\r
47 -(optional for GLib) PCRE (8.12 or later, building PCRE using CMake is
\r
48 recommended-please see build/win32/vs10/README.txt in the GLib source package)
\r
49 -(for gdk-pixbuf, if GDI+ is not to be used) IJG JPEG
\r
50 -(for gdk-pixbuf, if GDI+ is not to be used) jasper [JPEG-2000 library]
\r
51 -(for gdk-pixbuf, if GDI+ is not to be used, requires zlib and IJG JPEG) libtiff
\r
57 The "install" project will copy build results and headers into their
\r
58 appropriate location under <root>\vs10\<PlatformName>. For instance,
\r
59 built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into
\r
60 <root>\vs10\<PlatformName>\lib and Cogl headers into
\r
61 <root>\vs10\<PlatformName>\include\Cogl-2.0.
\r
63 *There is no known official VS10 build support for fontconfig
\r
64 (required for Pango and Pango at the moment-I will see whether this
\r
65 requirement can be made optional for VS builds)
\r
66 (along with freetype and expat) and gettext-runtime, so
\r
67 please use the binaries from:
\r
69 ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
\r
70 ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
\r
72 --Chun-wei Fan <fanc999@yahoo.com.tw>
\r
73 (Adopted from the GTK+ Win32 VS README.txt file originally by Tor Lillqvist)
\r