-
Notifications
You must be signed in to change notification settings - Fork 10
/
INSTALL.gwyddion
165 lines (125 loc) · 5.63 KB
/
INSTALL.gwyddion
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
Contents:
0. Prebuilt binaries
1. From sources -- Linux/Unix
2. From sources -- MS Windows
3. From sources -- Mac OS X
4. From Subversion (Linux/Unix only)
5. Pygwy under MS Windows
6. Modules and plug-ins
===[ 0. Prebuilt binaries ]==================================================
Binary packages provided by us, i.e. installers from MS Windows, require no
additional setup after standard package installation procedure. If you have
never installed Gwyddion (or other Gtk+ application), you will need to
install of Gtk+ runtime libraries prior to Gwyddion installation, we
recommend GladeWin32 packages.
We cannot tell for packages provided for other systems by other entities, but
do not expect them to require any additional setup either.
===[ 1. From sources -- Linux/Unix ]=========================================
See the section Build Dependencies of the Gwyddion user guide for the list
and description of required and optional packages.
Read generic GNU installation instruction in INSTALL that describe the build
process, common program arguments, and important environment variables.
Quick instructions:
Unpack tarball with sources, cd to the created directory, then run:
./configure
make
and as root run:
make install
If you have Gtk+ (or other packages, e.g., FFTW) in a nonstandard directory,
assure PKG_CONFIG_PATH environment variable points to directory where
gtk+-2.0.pc (e.g.) resides.
If you install to a subdirectory of home, you will probably use option
--enable-home-installation of ./configure to put desktop integration files
into the right places specified by XDG (i.e. outside the prefix).
To prevent the installation of GConf schemas, even though you have enabled the
GNOME thumbnailer, run `make install DISABLE_GCONF_SCHEMAS_INSTALL=yes'. To
ease packaging, it is automatically disabled when DESTDIR is non-empty.
===[ 2. Cross compilation for MS Windows ]===================================
See the user guide.
===[ 3. From sources -- Mac OS X ]===========================================
Essentially, the Unix instructions apply here too.
It's recommended to use Darwinports for installing the dependencies. You
need to install ports for gtk2, pkg-config; that should pull all the other
dependencies. It is recommended to install gtkglext and libxml2 too.
To make sure headers and libraries are found where Darwinports install them
you may want to explicitely set:
CFLAGS='-I/opt/local/include -I/usr/X11R6/include'
LDFLAGS='-L/opt/local/lib -I/usr/X11R6/lib'
Also make sure /opt/local/bin is in the PATH so that pkg-config can be found.
Note until Gtk+ Quartz port is finished, it's necessary to start an X11
server before running Gwyddion.
===[ 4. From Subversion (Linux/Unix only) ]==================================
The Subversion repository generally doesn't contain generated files, no
matter how unusual tools may be needed to generate them. Consider use of
nightly snapshot tarballs available at
http://gwyddion.net/download.php#head
Prerequisities:
- everything needed for compilation from tarballs
- GNU autoconf 2.60 or newer
- GNU automake 1.11 or newer
- GNU libtool 1.4 or newer
- Python-2.2 or newer
- Perl5
- gtk-doc 1.8 or newer
- GNU gettext 0.12 or newer, including development stuff
- who knows what else
First of all run
./autogen.sh
with any options you'd give to ./configure, note it always adds
--enable-maintainer-mode. You should add at least --enable-gtk-doc to
build the API documentation (tarballs cannot be made without it).
You should be able to build executables then with
make
At this point that all files that are included in source tarball should be
created, and
make install
or
make dist
will work as expected.
===[ 5. Pygwy under MS Windows ]=============================================
1. Python 2.4.X
Get Python sources
Unpack it for example to D:\
Open workspace $PYTHON_DIR\PC\VC6\pcbuild.dsw in Visual Studio 6
Set 'pythoncore' as active project
Choose Release configuration using Build/Set Active Configuration menu
Build python24.dll
2. Pygobject 2.12.X
If GTK is not installed, install its development version.
In MSVC 6 check and possibly add in Tools/Options/Directories
following Include files directories (GTK directories should already be
set in case you allowed the GTK installer to do it):
D:\GTK\INCLUDE
D:\GTK\INCLUDE\GTK-2.0
D:\GTK\INCLUDE\GLIB-2.0
D:\GTK\INCLUDE\PANGO-1.0
D:\GTK\INCLUDE\CAIRO
D:\GTK\INCLUDE\ATK-1.0
D:\GTK\INCLUDE\GTKGLEXT-1.0
D:\GTK\LIB\GTK-2.0\INCLUDE
D:\GTK\LIB\GTK-2.0\INCLUDE
D:\GTK\LIB\GLIB-2.0\INCLUDE
D:\GTK\LIB\GTKGLEXT-1.0\INCLUDE
D:\GTK\INCLUDE\LIBGLADE-2.0
D:\GTK\INCLUDE\LIBXML2
D:\PYTHON-2.4.4\INCLUDE
D:\PYTHON-2.4.4\PC
Library files:
D:\GTK\LIB
D:\PYTHON-2.4.4\PC\VC6
Note: Don't forget to use your own path to GTK and Python directories.
Get pygobject sources
Unpack it for example to D:\
Use provided workspace and project file (pygobject.dsp, pygobject.dsw)
and put them into pygobject directory.
Open workspace $PYGOBJECT_DIR\pygobject.dsw in Visual Studio 6
Choose Release configuration using Build/Set Active Configuration menu
Build pygobject.dll
3. Gwyddion
Set path variables (PYTHON_TOP, PYGOBJECT_TOP) in make.msc to coresponding
values and enable pygwy by uncommenting ENABLE_PYGWY variable.
Compile & install
Note: to see messages printed by Python interpreter to stdout you can add
/subsystem:console to LDFLAGS in make.msc and recompile & reinstall Gwyddion.
===[ 6. Modules and plug-ins ]===============================================
To be written.