| 1 |
Note that all this is rather experimental. |
| 2 |
|
| 3 |
A more detailed description on using Visual C++ to compile Clutter with |
| 4 |
its dependencies can be found on the following GNOME Live! page: |
| 5 |
|
| 6 |
https://wiki.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack |
| 7 |
|
| 8 |
Please do not attempt to compile Clutter in a path that contains spaces |
| 9 |
to avoid potential problems during compilation, linking or usage. |
| 10 |
|
| 11 |
This VS9 solution and the projects it includes are intented to be used |
| 12 |
in a Clutter source tree unpacked from a tarball. In a git checkout you |
| 13 |
first need to use some Unix-like environment or manual work to expand |
| 14 |
the files needed, like config.h.win32.in into config.h.win32 and the |
| 15 |
.vcprojin files here into corresponding actual .vcproj files. |
| 16 |
|
| 17 |
You will need the parts from GNOME: Cogl, JSON-GLib, GDK-Pixbuf, |
| 18 |
Pango*, atk and GLib. External dependencies are at least zlib, libpng, |
| 19 |
gettext-runtime* and Cairo*, and glext.h from |
| 20 |
http://www.opengl.org/registry/api/glext.h (which need to be in the GL folder |
| 21 |
in your include directories or in <root>\vs9\<PlatformName>\include\GL). |
| 22 |
|
| 23 |
Please see the README file in the root directory of this Clutter source package |
| 24 |
for the versions of the dependencies required. See also |
| 25 |
build-aux/win32/vs9/README.txt in the GLib source package for details |
| 26 |
where to unpack them. It is recommended that at least the dependencies |
| 27 |
from GNOME are also built with VS9 to avoid crashes caused by mixing different |
| 28 |
CRTs-please see also the build-aux/win32/vs9/README.txt in those respective |
| 29 |
packages. |
| 30 |
|
| 31 |
The recommended build sequence of the dependencies are as follows (the non-GNOME |
| 32 |
packages that are not downloaded as binaries from ftp://ftp.gnome.org have |
| 33 |
makefiles and/or VS project files that can be used to compile with VS directly, |
| 34 |
except the optional PCRE, which is built on VS using CMake; GLib & ATK have |
| 35 |
VS9 project files in the latest stable versions, GDK-Pixbuf have VS9 project files |
| 36 |
in the latest unstable version, and JSON-GLib, Pango and Cogl should have VS9 |
| 37 |
project files in the next unstable release): |
| 38 |
-Unzip the binary packages for gettext-runtime, freetype, expat and fontconfig |
| 39 |
downloaded from ftp://ftp.gnome.org* |
| 40 |
-zlib |
| 41 |
-libpng |
| 42 |
-(optional for GLib) PCRE (8.12 or later, building PCRE using CMake is |
| 43 |
recommended-please see build-aux/win32/vs9/README.txt in the GLib source package) |
| 44 |
-(for gdk-pixbuf, if GDI+ is not to be used) IJG JPEG |
| 45 |
-(for gdk-pixbuf, if GDI+ is not to be used) jasper [JPEG-2000 library] |
| 46 |
-(for gdk-pixbuf, if GDI+ is not to be used, requires zlib and IJG JPEG) libtiff |
| 47 |
-GLib |
| 48 |
-Cairo |
| 49 |
-Pango |
| 50 |
-ATK |
| 51 |
-GDK-Pixbuf |
| 52 |
-JSON-GLib |
| 53 |
-Cogl |
| 54 |
(Note that Pango, ATK, GDK-Pixbuf and JSON-GLib are not dependent on each |
| 55 |
other, so building them in any order will do) |
| 56 |
|
| 57 |
Note that a working PERL installation (such as ActiveState or Strawberry PERL) |
| 58 |
is also required for compilation of Clutter, as the glib-mkenums PERL utility |
| 59 |
script available from the GLib package will be used. Please ensure that the |
| 60 |
PERL interpretor is in your PATH. If a glib-mkenums script is not available, |
| 61 |
please extract glib-mkenums.in from the gobject subdirectory of the |
| 62 |
GLib source package, and change the lines and save as glib-mkenums in |
| 63 |
<root>\vs9\<PlatformName>\bin: |
| 64 |
|
| 65 |
#! @PERL_PATH@ (circa line 1) |
| 66 |
to |
| 67 |
#! c:/perl/bin (or whereever your PERL interpretor executable is) |
| 68 |
|
| 69 |
-and- |
| 70 |
|
| 71 |
print "glib-mkenums version glib-@GLIB_VERSION@\n"; |
| 72 |
to |
| 73 |
print "glib-mkenums version glib-<your GLib version>\n"; |
| 74 |
|
| 75 |
The "install" project will copy build results and headers into their |
| 76 |
appropriate location under <root>\vs9\<PlatformName>. For instance, |
| 77 |
built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into |
| 78 |
<root>\vs9\<PlatformName>\lib and Clutter headers into |
| 79 |
<root>\vs9\<PlatformName>\include\clutter-1.0. |
| 80 |
|
| 81 |
*There is no known official VS9 build support for fontconfig |
| 82 |
(required for Pango and Pango at the moment-I will see whether this |
| 83 |
requirement can be made optional for VS builds) |
| 84 |
(along with freetype and expat) and gettext-runtime, so |
| 85 |
please use the binaries from: |
| 86 |
|
| 87 |
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit) |
| 88 |
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit) |
| 89 |
|
| 90 |
Note: If you see C4819 warnings and you are compiling Clutteron a DBCS |
| 91 |
(Chinese/Korean/Japanese) version of Windows, you may need to switch |
| 92 |
to an English locale in Control Panel->Region and Languages->System-> |
| 93 |
Change System Locale, reboot and rebuild to ensure Clutter and its |
| 94 |
dependencies are built correctly. This is due to a bug in Visual C++ |
| 95 |
running on DBCS locales. |
| 96 |
|
| 97 |
--Chun-wei Fan <[email protected]> |
| 98 |
(Adopted from the GTK+ Win32 VS README.txt file originally by Tor Lillqvist) |