Skip to content
Newer
Older
100644 236 lines (161 sloc) 9.41 KB
27ca365 @dieterv Huge improvements in:
authored
1 ====================================
2 Using the PyGTK All-in-one installer
3 ====================================
5c4ed97 @dieterv first commit
authored
4
4649817 @dieterv README: clarify some things
authored
5
27ca365 @dieterv Huge improvements in:
authored
6 The PyGTK All-in-one version number
7 ===================================
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
8
8954b91 @dieterv prepare the README file for the first public release
authored
9 The PyGTK All-in-one installers' version number does not map directly to the
10 PyGTK version number. This is a requirement to support windows installer
27ca365 @dieterv Huge improvements in:
authored
11 major upgrades. The version number is constructed as follows::
5c4ed97 @dieterv first commit
authored
12
27ca365 @dieterv Huge improvements in:
authored
13 PYGTK_MAJOR.PYGTK_MINOR.INSTALLER_REVISION
14
15
16 What file should I use?
17 =======================
18
4649817 @dieterv README: clarify some things
authored
19 All the .msi files are named as follows::
27ca365 @dieterv Huge improvements in:
authored
20
3078698 @dieterv Update README and TODO file
authored
21 pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
27ca365 @dieterv Huge improvements in:
authored
22
3078698 @dieterv Update README and TODO file
authored
23 Where X.X.X is the PyGTK All-in-one version number, YY is 32 or 64 and
4649817 @dieterv README: clarify some things
authored
24 Z.Z is the Python version number the installer supports. Currently, only
3690296 @dieterv README: more clarification
authored
25 32 bit Python is supported (on both 32 and 64 bit Windows).
3078698 @dieterv Update README and TODO file
authored
26
27 You need to make sure both YY and Z.Z correspond to the version of the Python
28 interpreter that's installed on your system.
27ca365 @dieterv Huge improvements in:
authored
29
4649817 @dieterv README: clarify some things
authored
30
1641238 @dieterv add a getting started section
authored
31 I'm new, how do I start?
32 ========================
33
34 First, you'll need to install a 32 bit Python interpreter. Currently, you can
35 choose between Python 2.6 and Python 2.7.
36
8c002be @dieterv Fix python.org link
authored
37 - From http://www.python.org:
1641238 @dieterv add a getting started section
authored
38
aac3b18 @dieterv Fix download lists
authored
39 - http://www.python.org/download/releases/
40 - http://www.python.org/ftp/python/2.6.6/python-2.6.6.msi
41 - http://www.python.org/ftp/python/2.7.1/python-2.7.1.msi
1641238 @dieterv add a getting started section
authored
42
aac3b18 @dieterv Fix download lists
authored
43 - From http://www.activestate.com/activepython:
44
45 - http://www.activestate.com/activepython/downloads
46 - http://downloads.activestate.com/ActivePython/releases/2.6.6.17/ActivePython-2.6.6.17-win32-x86.msi
47 - http://downloads.activestate.com/ActivePython/releases/2.7.1.3/ActivePython-2.7.1.3-win32-x86.msi
1641238 @dieterv add a getting started section
authored
48
49
50 Then you install the PyGTK All-in-one version that matches the Python version
51 you choose above. It's that easy!
52
53
8954b91 @dieterv prepare the README file for the first public release
authored
54 Migrating from PyGTK+PyGObject+PyCairo packages
27ca365 @dieterv Huge improvements in:
authored
55 ===============================================
56
8954b91 @dieterv prepare the README file for the first public release
authored
57 If you have used some or all of the separate PyGTK, PyGObject, PyGooCanvas,
58 PyGtkSourceView2, PyRsvg and PyCairo packages before, please ensure they are
59 uninstalled before you begin with the PyGTK All-in-one installer.
27ca365 @dieterv Huge improvements in:
authored
60
61 The all-in-one installer does not check for their presence and will happily
62 overwrite files that belong to the separate packages. If you forget to check
63 for this you risk the following scenario:
64
65 - install Python
8954b91 @dieterv prepare the README file for the first public release
authored
66 - install PyCairo, PyGTK and PyGObject
67 - install PyGTK All-in-one
68 - uninstall PyCairo, PyGTK and PyGObject
4649817 @dieterv README: clarify some things
authored
69 - you now have a *broken* pygtk all-in-one installation
27ca365 @dieterv Huge improvements in:
authored
70
8954b91 @dieterv prepare the README file for the first public release
authored
71 This would also be a good time to remove the GTK+ runtime you've used with the
72 separate PyG* packages and to clean your PATH environment variable.
3078698 @dieterv Update README and TODO file
authored
73
8954b91 @dieterv prepare the README file for the first public release
authored
74 Note that the PyCaio, PyGObject, PyGTK, PyGoocanvas, PyGtkSourceView2 and PyRsvg
3078698 @dieterv Update README and TODO file
authored
75 .exe installers (like any other .exe installer generated by distutils) sometimes
4649817 @dieterv README: clarify some things
authored
76 leave things behind when you uninstall them.
77
27ca365 @dieterv Huge improvements in:
authored
78
3078698 @dieterv Update README and TODO file
authored
79 Default installation
80 ====================
27ca365 @dieterv Huge improvements in:
authored
81
3078698 @dieterv Update README and TODO file
authored
82 A default PyGTK All-in-one installation automatically detects the correct
27ca365 @dieterv Huge improvements in:
authored
83 Python installation directory and if Python was installed for all users or just
84 yourself. These values are then used by the PyGTK All-in-one installer.
3078698 @dieterv Update README and TODO file
authored
85 To start a default PyGTK All-in-one installation, simply double click the
86 .msi file or execute the following command from a Command Prompt (cmd.exe)::
27ca365 @dieterv Huge improvements in:
authored
87
3078698 @dieterv Update README and TODO file
authored
88 %WINDIR%\system32\msiexec.exe /i pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
27ca365 @dieterv Huge improvements in:
authored
89
4649817 @dieterv README: clarify some things
authored
90
3078698 @dieterv Update README and TODO file
authored
91 Custom installation
92 ===================
27ca365 @dieterv Huge improvements in:
authored
93
3078698 @dieterv Update README and TODO file
authored
94 Like any other Windows Installer package, you can change how PyGTK All-in-one
eb3ec96 @dieterv clarify msiexec "parameters"
authored
95 will be installed on you system by passing parameters (setting public properties
96 for those familiar with windows installer). Execute `msiexec /help` for a list
97 of options supported for all .msi installation packages.
27ca365 @dieterv Huge improvements in:
authored
98
3078698 @dieterv Update README and TODO file
authored
99 Target directory
100 ----------------
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
101
3078698 @dieterv Update README and TODO file
authored
102 The TARGETDIR property determines the root directory of the PyGTK All-in-one
103 installation. If this property is set, the PyGTK All-in-one installer does
104 not automatically detect the installation directory of the Python interpreter
105 installed on you system. For example, a custom installation directory can be
106 specified with::
107
108 TARGETDIR=R:\pythonX
109
8954b91 @dieterv prepare the README file for the first public release
authored
110 Before you set a custom TARGETDIR property, you need to make sure both python.exe
111 and pythonw.exe exist in that directory or the installation will fail.
112
3078698 @dieterv Update README and TODO file
authored
113 Installation for All Users
114 --------------------------
115
116 The ALLUSERS property determines if PyGTK All-in-one should be installed for
117 all users, or only for the user that initiated the installation. If you want
118 to install for all users, set the ALLUSERS property to "1"::
119
120 ALLUSERS=1
121
122 If you want to install for the current user only, you should not specify the
123 ALLUSERS property at all. Hence, a per user installation is the default installation
124 mode for custom installations. Note that "1" is the only valid value for the
125 ALLUSERS property!
126
8954b91 @dieterv prepare the README file for the first public release
authored
127 You need to combine this property with the TARGETDIR property. Setting ALLUSERS
128 disables the automatic Python interpreter detection.
3078698 @dieterv Update README and TODO file
authored
129
130 Feature Selection
131 -----------------
132
133 The INSTALLLEVEL property determines what features are going to be installed. If
134 the INSTALLLEVEL property is not set, it's value defaults to 1 which causes a
8954b91 @dieterv prepare the README file for the first public release
authored
135 basic set of features to be installed (GTK+ runtime, PyGTK, PyGObject and PyCairo)
3078698 @dieterv Update README and TODO file
authored
136
137 If you set INSTALLLEVEL to 2 (or any number greater than 2), you instruct the
138 installer to do a "complete" installation (all features will be installed).
139
140 There is another method to control what features should be installed by controlling
141 the ADDLOCAL, REMOVE, ADDDEFAULT, REINSTALL, etc properties. Check MSDN for more
142 details.
143
144 Other msiexec options
145 ---------------------
146
8954b91 @dieterv prepare the README file for the first public release
authored
147 Take note that if the PyGTK All-in-one installer is run with no or a basic
148 UI (/q[n|b]) the automatic Python installation detection is skipped. In this
3078698 @dieterv Update README and TODO file
authored
149 case setting the TARGETDIR property is required. You can also set the ALLUSERS
150 property if you want a system wide installation.
151
4649817 @dieterv README: clarify some things
authored
152
3078698 @dieterv Update README and TODO file
authored
153 The PATH environment variable
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
154 =============================
155
3078698 @dieterv Update README and TODO file
authored
156 The PyGTK All-in-one installer does not require you to fiddle with the PATH
8954b91 @dieterv prepare the README file for the first public release
authored
157 environment variable. The PyGTK version that's installed with the all-in-one
158 installer takes care of loading the bundled GTK+ runtime on the PATH environment
3078698 @dieterv Update README and TODO file
authored
159 variable on interpreter startup. As a consequence simply importing gobject,
4649817 @dieterv README: clarify some things
authored
160 gtk, etc works out of the box. And as an added advantage there is no possible way
8954b91 @dieterv prepare the README file for the first public release
authored
161 multiple GTK+ runtime versions on your system or user PATH environment variable
162 can interfere with PyGTK All-in-one.
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
163
4649817 @dieterv README: clarify some things
authored
164
3078698 @dieterv Update README and TODO file
authored
165 Getting help
166 ============
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
167
3078698 @dieterv Update README and TODO file
authored
168 If something doesn't work as expected, you'll need to generate a couple of log
169 files before you'll be able to get help. It is simply impossible to determine
4649817 @dieterv README: clarify some things
authored
170 why something went wrong without these log files.
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
171
4649817 @dieterv README: clarify some things
authored
172 If something went wrong when installing, you'll need both:
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
173
3078698 @dieterv Update README and TODO file
authored
174 - An installation log (install.log). Execute the following command from a Command Prompt (cmd.exe)::
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
175
3078698 @dieterv Update README and TODO file
authored
176 %WINDIR%\system32\msiexec.exe -i pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi /l*vx install.log
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
177
3078698 @dieterv Update README and TODO file
authored
178 - An execution log (import.log). Execute the following command from a Command Prompt (cmd.exe)::
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
179
3078698 @dieterv Update README and TODO file
authored
180 python -v -c "import gtk">import.log 2>&1
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
181
3078698 @dieterv Update README and TODO file
authored
182 If something went wrong when uninstalling, you'll need an unistall log. Execute
183 the following command from a Command Prompt (cmd.exe)::
5fcfef1 @dieterv Fix TARGETDIR handling...
authored
184
3078698 @dieterv Update README and TODO file
authored
185 %WINDIR%\system32\msiexec.exe -x pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi /l*vx uninstall.log
dbad5ac @dieterv Add known issues section to the README
authored
186
4649817 @dieterv README: clarify some things
authored
187 Please consider compressing the log files you obtained before you send them
188 by mail or attach them to a bug report. Those files can be quite large.
317491a @dieterv README: fix a typo
authored
189 If you do not have a compression program yet, 7-Zip from http://www.7-zip.org/
4649817 @dieterv README: clarify some things
authored
190 is a good choice.
191
192
193 Known issues
194 ============
dbad5ac @dieterv Add known issues section to the README
authored
195
196 - The bundled svg_pixbuf_loader does not seem to be compatible with the new,
f6e8daf @dieterv Created a bug for the gdk-pixbuf problem
authored
197 split gdk-pixbuf-2.22.0. Other svg functionality works fine. See
198 https://bugzilla.gnome.org/show_bug.cgi?id=637742
dbad5ac @dieterv Add known issues section to the README
authored
199
d5db758 @dieterv split win2k issues
authored
200 - In theory, Windows 2000 should be supported, but in practice the gtk+ binaries
201 on ftp.gnome.org are affected by libgio-2.0-0.dll needing the freeaddrinfo()
202 function wich is only available starting from Windows XP:
dbad5ac @dieterv Add known issues section to the README
authored
203
d5db758 @dieterv split win2k issues
authored
204 - https://bugzilla.gnome.org/show_bug.cgi?id=637565
205 - related bug: https://bugzilla.gnome.org/show_bug.cgi?id=610502#c6
206 - related bug: https://bugzilla.gnome.org/show_bug.cgi?id=623128
207 - http://msdn.microsoft.com/en-us/library/ms737931%28v=vs.85%29.aspx
4649817 @dieterv README: clarify some things
authored
208
209 - On Windows 2000 you need gdiplus.dll:
210
211 - Download the GDI+ Platform SDK redistributable from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6a63ab9c-df12-4d41-933c-be590feaa05a&displaylang=en
212 - Execute the downloaded WindowsXP-KB975337-x86-ENU.exe and it will ask to extract some files.
213 - Copy the extracted asms\\10\\msft\\windows\\gdiplus\\gdiplus.dll file to C:\\Python2X\\Lib\\site-packages\\gtk-2.0\\runtime\\bin
214
215
464f0c5 @dieterv README: put the the interesting stuff on top and the about section at…
authored
216 =================================
217 About the pygtk-installer project
218 =================================
219
220 The pygtk-installer project provides a set of tools to build the PyGTK
221 All-in-one installer and it's various dependencies.
222 There are currently versions of the PyGTK All-in-one installer supporting 32 bit
223 versions of Python 2.6 and Python 2.7.
224
225 Included tools:
226
227 - build_glade.sh: a tool that builds glade3 binaries for mswindows with
228 "Python Widgets Support" for each supported Python version.
229 - build_bindings.sh: a tool that builds windows installer packages (both .exe
230 and .msi) for pycairo, pygobject, pygtk, pygoocanvas, pygtksourceview and
231 pyrsvg for each supported Python version.
232 - build_installer.py: a tool that generates the all-in-one installer bundling
233 the separate .msi installers created by build_bindings.sh, the glade binaries
234 created by build_glade.sh and various GTK+ runtime packages from
235 ftp.gnome.org/pub/GNOME/binaries/win32/.
Something went wrong with that request. Please try again.