Skip to content
This repository
Newer
Older
100644 202 lines (143 sloc) 8.344 kb
8954b915 »
2010-12-18 prepare the README file for the first public release
1 =================================
2 About the pygtk-installer project
3 =================================
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
4
8954b915 »
2010-12-18 prepare the README file for the first public release
5 The pygtk-installer project provides a set of tools to build the PyGTK
6 All-in-one installer and it's various dependencies.
7 There are currently versions of the PyGTK All-in-one installer supporting 32 bit
8 versions of Python 2.6 and Python 2.7.
9
10 Included tools:
11
12 - build_glade.sh: a tool that builds glade3 binaries for mswindows with
13 "Python Widgets Support" for each supported Python version.
14 - build_bindings.sh: a tool that builds windows installer packages (both .exe
15 and .msi) for pycairo, pygobject, pygtk, pygoocanvas, pygtksourceview and
16 pyrsvg for each supported Python version.
17 - build_installer.py: a tool that generates the all-in-one installer bundling
18 the separate .msi installers created by build_bindings.sh, the glade binaries
19 created by build_glade.sh and various GTK+ runtime packages from
20 ftp.gnome.org/pub/GNOME/binaries/win32/.
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
21
27ca365e »
2010-12-03 Huge improvements in:
22 ====================================
23 Using the PyGTK All-in-one installer
24 ====================================
5c4ed978 »
2010-11-12 first commit
25
27ca365e »
2010-12-03 Huge improvements in:
26 The PyGTK All-in-one version number
27 ===================================
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
28
8954b915 »
2010-12-18 prepare the README file for the first public release
29 The PyGTK All-in-one installers' version number does not map directly to the
30 PyGTK version number. This is a requirement to support windows installer
27ca365e »
2010-12-03 Huge improvements in:
31 major upgrades. The version number is constructed as follows::
5c4ed978 »
2010-11-12 first commit
32
27ca365e »
2010-12-03 Huge improvements in:
33 PYGTK_MAJOR.PYGTK_MINOR.INSTALLER_REVISION
34
35 Stable releases are kept available for download, testing revisions are removed
36 from the download area once they are superseded by newer versions.
37
38 What file should I use?
39 =======================
40
41 All the .msi files are named as follows:
42
3078698b »
2010-12-11 Update README and TODO file
43 pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
27ca365e »
2010-12-03 Huge improvements in:
44
3078698b »
2010-12-11 Update README and TODO file
45 Where X.X.X is the PyGTK All-in-one version number, YY is 32 or 64 and
46 Z.Z is the Python version number the installer supports.
47
48 You need to make sure both YY and Z.Z correspond to the version of the Python
49 interpreter that's installed on your system.
27ca365e »
2010-12-03 Huge improvements in:
50
16412380 »
2010-12-18 add a getting started section
51 I'm new, how do I start?
52 ========================
53
54 First, you'll need to install a 32 bit Python interpreter. Currently, you can
55 choose between Python 2.6 and Python 2.7.
56
8c002be7 »
2010-12-18 Fix python.org link
57 - From http://www.python.org:
16412380 »
2010-12-18 add a getting started section
58
aac3b18f »
2010-12-18 Fix download lists
59 - http://www.python.org/download/releases/
60 - http://www.python.org/ftp/python/2.6.6/python-2.6.6.msi
61 - http://www.python.org/ftp/python/2.7.1/python-2.7.1.msi
16412380 »
2010-12-18 add a getting started section
62
aac3b18f »
2010-12-18 Fix download lists
63 - From http://www.activestate.com/activepython:
64
65 - http://www.activestate.com/activepython/downloads
66 - http://downloads.activestate.com/ActivePython/releases/2.6.6.17/ActivePython-2.6.6.17-win32-x86.msi
67 - http://downloads.activestate.com/ActivePython/releases/2.7.1.3/ActivePython-2.7.1.3-win32-x86.msi
16412380 »
2010-12-18 add a getting started section
68
69
70 Then you install the PyGTK All-in-one version that matches the Python version
71 you choose above. It's that easy!
72
73 Note: There are currently no 64 bit builds of PyGTK All-in-one!
74
8954b915 »
2010-12-18 prepare the README file for the first public release
75 Migrating from PyGTK+PyGObject+PyCairo packages
27ca365e »
2010-12-03 Huge improvements in:
76 ===============================================
77
8954b915 »
2010-12-18 prepare the README file for the first public release
78 If you have used some or all of the separate PyGTK, PyGObject, PyGooCanvas,
79 PyGtkSourceView2, PyRsvg and PyCairo packages before, please ensure they are
80 uninstalled before you begin with the PyGTK All-in-one installer.
27ca365e »
2010-12-03 Huge improvements in:
81
82 The all-in-one installer does not check for their presence and will happily
83 overwrite files that belong to the separate packages. If you forget to check
84 for this you risk the following scenario:
85
86 - install Python
8954b915 »
2010-12-18 prepare the README file for the first public release
87 - install PyCairo, PyGTK and PyGObject
88 - install PyGTK All-in-one
89 - uninstall PyCairo, PyGTK and PyGObject
27ca365e »
2010-12-03 Huge improvements in:
90 you now have a *broken* pygtk all-in-one installation
91
8954b915 »
2010-12-18 prepare the README file for the first public release
92 This would also be a good time to remove the GTK+ runtime you've used with the
93 separate PyG* packages and to clean your PATH environment variable.
3078698b »
2010-12-11 Update README and TODO file
94
8954b915 »
2010-12-18 prepare the README file for the first public release
95 Note that the PyCaio, PyGObject, PyGTK, PyGoocanvas, PyGtkSourceView2 and PyRsvg
3078698b »
2010-12-11 Update README and TODO file
96 .exe installers (like any other .exe installer generated by distutils) sometimes
97 leaves things behind when you uninstall them.
27ca365e »
2010-12-03 Huge improvements in:
98
3078698b »
2010-12-11 Update README and TODO file
99 Default installation
100 ====================
27ca365e »
2010-12-03 Huge improvements in:
101
3078698b »
2010-12-11 Update README and TODO file
102 A default PyGTK All-in-one installation automatically detects the correct
27ca365e »
2010-12-03 Huge improvements in:
103 Python installation directory and if Python was installed for all users or just
104 yourself. These values are then used by the PyGTK All-in-one installer.
3078698b »
2010-12-11 Update README and TODO file
105 To start a default PyGTK All-in-one installation, simply double click the
106 .msi file or execute the following command from a Command Prompt (cmd.exe)::
27ca365e »
2010-12-03 Huge improvements in:
107
3078698b »
2010-12-11 Update README and TODO file
108 %WINDIR%\system32\msiexec.exe /i pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
27ca365e »
2010-12-03 Huge improvements in:
109
3078698b »
2010-12-11 Update README and TODO file
110 Custom installation
111 ===================
27ca365e »
2010-12-03 Huge improvements in:
112
3078698b »
2010-12-11 Update README and TODO file
113 Like any other Windows Installer package, you can change how PyGTK All-in-one
eb3ec969 »
2010-12-15 clarify msiexec "parameters"
114 will be installed on you system by passing parameters (setting public properties
115 for those familiar with windows installer). Execute `msiexec /help` for a list
116 of options supported for all .msi installation packages.
27ca365e »
2010-12-03 Huge improvements in:
117
3078698b »
2010-12-11 Update README and TODO file
118 Target directory
119 ----------------
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
120
3078698b »
2010-12-11 Update README and TODO file
121 The TARGETDIR property determines the root directory of the PyGTK All-in-one
122 installation. If this property is set, the PyGTK All-in-one installer does
123 not automatically detect the installation directory of the Python interpreter
124 installed on you system. For example, a custom installation directory can be
125 specified with::
126
127 TARGETDIR=R:\pythonX
128
8954b915 »
2010-12-18 prepare the README file for the first public release
129 Before you set a custom TARGETDIR property, you need to make sure both python.exe
130 and pythonw.exe exist in that directory or the installation will fail.
131
3078698b »
2010-12-11 Update README and TODO file
132 Installation for All Users
133 --------------------------
134
135 The ALLUSERS property determines if PyGTK All-in-one should be installed for
136 all users, or only for the user that initiated the installation. If you want
137 to install for all users, set the ALLUSERS property to "1"::
138
139 ALLUSERS=1
140
141 If you want to install for the current user only, you should not specify the
142 ALLUSERS property at all. Hence, a per user installation is the default installation
143 mode for custom installations. Note that "1" is the only valid value for the
144 ALLUSERS property!
145
8954b915 »
2010-12-18 prepare the README file for the first public release
146 You need to combine this property with the TARGETDIR property. Setting ALLUSERS
147 disables the automatic Python interpreter detection.
3078698b »
2010-12-11 Update README and TODO file
148
149 Feature Selection
150 -----------------
151
152 The INSTALLLEVEL property determines what features are going to be installed. If
153 the INSTALLLEVEL property is not set, it's value defaults to 1 which causes a
8954b915 »
2010-12-18 prepare the README file for the first public release
154 basic set of features to be installed (GTK+ runtime, PyGTK, PyGObject and PyCairo)
3078698b »
2010-12-11 Update README and TODO file
155
156 If you set INSTALLLEVEL to 2 (or any number greater than 2), you instruct the
157 installer to do a "complete" installation (all features will be installed).
158
159 There is another method to control what features should be installed by controlling
160 the ADDLOCAL, REMOVE, ADDDEFAULT, REINSTALL, etc properties. Check MSDN for more
161 details.
162
163 Other msiexec options
164 ---------------------
165
8954b915 »
2010-12-18 prepare the README file for the first public release
166 Take note that if the PyGTK All-in-one installer is run with no or a basic
167 UI (/q[n|b]) the automatic Python installation detection is skipped. In this
3078698b »
2010-12-11 Update README and TODO file
168 case setting the TARGETDIR property is required. You can also set the ALLUSERS
169 property if you want a system wide installation.
170
171 The PATH environment variable
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
172 =============================
173
3078698b »
2010-12-11 Update README and TODO file
174 The PyGTK All-in-one installer does not require you to fiddle with the PATH
8954b915 »
2010-12-18 prepare the README file for the first public release
175 environment variable. The PyGTK version that's installed with the all-in-one
176 installer takes care of loading the bundled GTK+ runtime on the PATH environment
3078698b »
2010-12-11 Update README and TODO file
177 variable on interpreter startup. As a consequence simply importing gobject,
8954b915 »
2010-12-18 prepare the README file for the first public release
178 gtk, etc works out of the box. As an added advantage there is no possible way
179 multiple GTK+ runtime versions on your system or user PATH environment variable
180 can interfere with PyGTK All-in-one.
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
181
3078698b »
2010-12-11 Update README and TODO file
182 Getting help
183 ============
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
184
3078698b »
2010-12-11 Update README and TODO file
185 If something doesn't work as expected, you'll need to generate a couple of log
186 files before you'll be able to get help. It is simply impossible to determine
187 why something went wrong without those log files!
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
188
3078698b »
2010-12-11 Update README and TODO file
189 If something went wrong when installing, you'll need both
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
190
3078698b »
2010-12-11 Update README and TODO file
191 - An installation log (install.log). Execute the following command from a Command Prompt (cmd.exe)::
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
192
3078698b »
2010-12-11 Update README and TODO file
193 %WINDIR%\system32\msiexec.exe -i pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi /l*vx install.log
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
194
3078698b »
2010-12-11 Update README and TODO file
195 - An execution log (import.log). Execute the following command from a Command Prompt (cmd.exe)::
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
196
3078698b »
2010-12-11 Update README and TODO file
197 python -v -c "import gtk">import.log 2>&1
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
198
3078698b »
2010-12-11 Update README and TODO file
199 If something went wrong when uninstalling, you'll need an unistall log. Execute
200 the following command from a Command Prompt (cmd.exe)::
5fcfef19 »
2010-11-27 Fix TARGETDIR handling...
201
3078698b »
2010-12-11 Update README and TODO file
202 %WINDIR%\system32\msiexec.exe -x pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi /l*vx uninstall.log
Something went wrong with that request. Please try again.