28
28
something similar.)
30
30
If you are compiling from SVN, you will need libtool and the auto* tools
31
and will need to replace the configure above with bootstrap for the 2.5.x
32
version or bootstrap-2.4 for the 1.9.x version.
31
and will need to replace the configure above with bootstrap-2.n for whichever
32
API version you are building.
34
To build a win32 installer, cygwin is required. Use the mingw-gcc compiler
35
and ensure that the autotools are installed, but do not install any of the
36
gtk+ libraries from cygwin. You will need to get the zip bundles for gtk+
37
and dependencies, along with libglade and libxml2 from:
39
ftp.gnome.org/pub/gnome/binaries
41
for the platform you are building. Extract all these zips, including the devel
42
zips into a single directory and setup your path so that it can access the
43
pkg-config tool provided. You will also want to edit the lib/pkgconfig/*.pc
44
files to specify the prefix you installed to.
46
Once all that is done, configure away.
48
There is a special make target which supports the process of building msi
49
installers. You can make installer-bundle to create a subdirectory named
50
gtk-sharp-binaries-<version> which will contain a wxs script and all the
51
binaries from the build. You will also need to copy into this directory the
52
msm modules for gtk+, libglade, and mono-cairo. These can be built
53
from svn trunk module win32-installers. Once those msm's are in place,
54
execute the build-installer script to produce the msi.
35
56
Discussion & Support:
36
57
---------------------
added
removed
README
