Skip to content

HTTPS clone URL

Subversion checkout URL

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