|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| MSVC_Net2013/ | H | 19-Aug-2016 | - | 1,216 | 1,060 |
| build/ | H | 19-Aug-2016 | - | 25,750 | 20,671 |
| docs/ | H | 03-May-2022 | - | 31,960 | 31,267 |
| pango/ | H | 19-Aug-2016 | - | 42,448 | 29,599 |
| tools/ | H | 03-May-2022 | - | 1,014 | 812 |
| AUTHORS | H A D | 09-Dec-2014 | 667 | 21 | 17 |
| COPYING | H A D | 09-Dec-2014 | 25.9 KiB | 516 | 435 |
| COPYING.tools | H A D | 09-Dec-2014 | 17.6 KiB | 340 | 281 |
| ChangeLog | H A D | 19-Aug-2016 | 39.1 KiB | 1,310 | 821 |
| INSTALL | H A D | 19-Aug-2016 | 15.4 KiB | 371 | 289 |
| Makefile.am | H A D | 17-Sep-2015 | 1.7 KiB | 53 | 26 |
| Makefile.in | H A D | 03-May-2022 | 34.5 KiB | 1,045 | 935 |
| NEWS | H A D | 19-Aug-2016 | 4.4 KiB | 195 | 133 |
| README | H A D | 09-Dec-2014 | 66 | 4 | 2 |
| README.SUN | H A D | 09-Dec-2014 | 2.7 KiB | 88 | 63 |
| README.win32 | H A D | 17-Sep-2015 | 2.4 KiB | 65 | 46 |
| aclocal.m4 | H A D | 19-Aug-2016 | 80.7 KiB | 2,461 | 2,159 |
| autogen.sh | H A D | 09-Dec-2014 | 261 | 8 | 5 |
| config.h.in | H A D | 19-Aug-2016 | 1.9 KiB | 71 | 47 |
| configure | H A D | 19-Aug-2016 | 623.5 KiB | 20,496 | 17,321 |
| configure.ac | H A D | 19-Aug-2016 | 3.3 KiB | 85 | 70 |
README
README.SUN
1Building gtkmm under Sun Solaris
2================================
3
4This README refers currently only to Sun Forte[tm] C++ compiler (WS6U2)
5under Solaris 8/Sparc.
6
7The described procedure to compile gtkmm with Sun's commercial C++
8compiler assumes the default compiler installation of Forte[tm] C++ 6
9update 2. Furthermore all currently available product and adequate SunOS
10patches for Forte[tm] C++ 6 update 2, which can be donwload from the
11links given at http://access1.sun.com/sundev/fdp6u2-patches.html, have
12to be applied. After that your compiler should give the following
13version information:
14
15 $ CC -V
16 CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-10 2002/09/16
17
18You will not be able to compile gtkmm with the unpatched compiler
19installation. Also, it is important to hide any gcc installation
20from your PATH.
21
22
23The installation procedure:
24
25* Recent versions of the following GNU utilities should be avalaible in
26 your PATH:
27
28 make (3.79.1)
29 libtool (1.4.2)
30 m4 (1.4)
31 perl (5.6.1)
32
33 The version information (in brackets) apply to my GNU installation.
34
35* Assuming your compiler installation is in /opt/SUNWspro, the following
36 environment changes are required:
37
38 PATH=/opt/SUNWspro/bin:$PATH
39 LD_LIBRARY_PATH=/opt/SUNWspro/bin:$LD_LIBRARY_PATH
40 export PATH LD_LIBRARY_PATH
41
42 CC="cc"
43 CXX="CC"
44 LD="CC"
45 CFLAGS="-g" or "-g -xO3" for better optimization
46 CXXFLAGS="-g" or "-g -O3" for better optimization
47 export CC CXX LD CFLAGS CXXFLAGS
48
49* Select an installation directory ($PREFIX).
50
51* The image libraries jpeg-6b, libpng-1.2.5 and tiff-v3.5.7 are pre-
52 requisites to build gtk+ libraries. They can be obtained from
53 www.sunfreeware.com or build from source. Compiling from source
54 requires some manual corrections (basically prefix settings in the
55 makefiles), because their build mechanism are rather old. All three
56 libraries should be build as shared libraries and installed to the
57 choosen installation directory.
58
59* gtk+-Installation. For each package of pkgconfig-0.12.0, glib-2.0.6,
60 atk-1.0.3, pango-1.0.4, gtk+-2.0.6 do:
61
62 cd <package-path>
63 CPPFLAGS=-I$PREFIX/include CFLAGS="-I$PREFIX/include $CFLAGS" \
64 ./configure --prefix=$PREFIX
65 make
66 make install
67
68* gtkmm-Installation. For each package of libsigc++-1.2.x, gtkmm-2.0.x do:
69
70 cd <package-path>
71 ./configure --prefix=$PREFIX
72 make
73 make install
74
75* Verification can easily done by
76
77 cd gtkmm-1.2.x/examples
78 make
79
80 and testing all built executables.
81
82
83Feel free to contact the gtkmm mailing list in case of problems compiling gtkmm under Sun
84Solaris.
85
86
87Michael v. Szombathely, 31-Oct-02
88<szombath@bifab.de>
README.win32
1Building gtkmm on Win32
2===========================
3
4Currently, both the mingw (native win32) gcc compiler and MS Visual
5Studio 2013 are supported. gtkmm can be built with mingw32-gcc using
6the gnu autotools (automake, autoconf, libtool). As explicitly
7stated in the gtk+ for win32 distribution (http://www.gimp.org/win32/),
8the gcc compiler provided by the cygwin distribution should not be
9used to build gtk+/gtkmm libraries and/or applications (see the
10README.win32 that comes with the gtk+ DLLs). This MIGHT cause
11conflicts between the cygwin and msvcrt runtime environments.
12
131. Mingw
14
15The mingw distribution which has been tested with this release is the
16following :
17
18* MinGW-4.1 as the base distribution.
19
20The bare mingw distribution does not provide the necessary tools (sh, perl, m4
21, autoconf, automake, ..) to run the provided configure script "as is". One
22(currently non supported) solution is to use mingw in conjunction with msys,
23which is readily available on the mingw website (http://www.mingw.org/).
24
25The preferred method is to combine the cygwin distribution (for the unix tools
26that were mentioned above) with mingw by making sure that the mingw
27tools (gcc, ld, dlltool, ..) are called first.
28
29First, make sure that you have working distribution of the native port
30of both libsigc++-2.0.x and gtk+-2.0 on win32 (see
31http://www.gimp.org/win32). If you can't compile a simple gtk+ example
32using gcc and `pkg-config --cflags --libs`, you should not even think
33about trying to compile gtkmm, let alone using precompiled libgtkmm
34DLLs to port your gtkmm application !
35
36The configure script can then be called using (as an example) the
37following options
38
39./configure --prefix=/target --build=i386-pc-mingw32 --disable-static
40
41then
42
43make
44make check
45make install
46
472. MS Visual Studio 2013
48
49Open the pangomm.sln solution file in the MSVC_Net2013 directory. In
50the Tools/Options panel, add the appropriate GTK+ and glibmm include
51and lib directories to the Projects and Solutions/VC++ directories,
52if they are not in the locations specified by the property sheets,
53i.e. $(srcroot)\..\vs12\$(Platform). Build the solution. The option
54/vd2 should not be used in these builds, unlike previous builds, as
55that would cause broken binaries to be built, causing crashes.
56
573. Gtkmm methods and signals not available on win32
58
59All gtkmm methods and signals are available on win32.
60
614. Gtkmm examples and demos on win32
62
63All demos and examples compile/run on win32
64
65