On Linux, Wing can be installed from RPM, Debian package, or from tar archive. Use the latter if you do not have root access on your machine or wish to install Wing somewhere other than /usr/lib/wingide4.1. Be sure to use the 64-bit packages if you are on a 64-bit system.
Installing from RPM:
Wing can be installed from an RPM package on RPM-based systems, such as RedHat and Mandriva. To install, run rpm -i wingide4.1-4.1.13-1.i386.rpm as root or use your favorite RPM administration tool to install the RPM. Most files for Wing are placed under the /usr/lib/wingide4.1 directory and the wing4.1 command is placed in the /usr/bin directory.
Installing from Debian package:
Wing can be installed from a Debian package on Debian, Ubuntu, and other Debian-based systems.
You will need to install enscript before installing Wing, if it's not already on your system.
To install, run dpkg -i wingide4.1_4.1.13-1_i386.deb
as root or use your favorite package administration tool to install. Most files for Wing are placed under the /usr/lib/wingide4.1 directory and the wing4.1 command is placed in the /usr/bin directory.
Installing from Tar Archive:
Wing may also be installed from a tar archive. This can be used on systems that do not use RPM or Debian packages, or if you wish to install Wing into a directory other than /usr/lib/wingide4.1. Unpacking this archive with tar -zxvf wingide-4.1.13-1-i386-linux.tar.gz will create a wingide-4.1.13-1-i386-linux directory that contains the wing-install.py script and a binary-package.tar file.
Running the wing-install.py script will prompt for the location to install Wing, and the location in which to place the executable wing4.1. These locations default to /usr/local/lib/wingide and /usr/local/bin, respectively. The install program must have read/write access to both of these directories, and all users running Wing must have read access to both.
Using System-wide GTK:
By default, Wing IDE runs with its own copy of GTK2 and does not pick up on the system-configured theme. This is done to avoid problems and bugs sometimes brought out by binary incompatibilities in GTK versions.
On Linux versions that include GTK version 2.6 or later, you can tell Wing IDE to use the system-defined GTK2 by setting the System GTK preference or running with the --system-gtk command line argument.
Using the system-wide GTK2 in this way generally works quite well but may result in crashing or display bugs due to binary incompatibilities in GTK and related libraries. If you set the preference and Wing fails to start, specify the --private-gtk command line option to override the preference.
Non-ascii File Paths on Older Linux Systems:
Some older Linux versions require setting the environment variable G_BROKEN_FILENAMES before Wing IDE's file open/save dialog will work properly with file paths that contain non-ascii characters. The environment variable is already set on some systems where it is needed but this is not always the case.
Debugging 32-bit Python on 64-bit Systems
On a 64-bit system where you need to debug 32-bit Python, you will need to install the 32-bit version of Wing. This version can also debug 64-bit Python.
Installing the 32-bit version of Wing may require installing some compatibility packages as follows:
On 64-bit Ubuntu and Debian systems, you need to first install the 32 bit compatibility libraries. This is the ia32-libs package on Ubuntu. On Debian and Ubuntu 9+, the ia32-libs-gtk package is needed as well. Then install the 32-bit Wing with the command dpkg -i --force-architecture --force-depends ~~PRODUCT_SPEC_VERSION~~_~~FULL_VERSION~~-~~BUILD~~_.i386.deb The package contains what you need to run your debug process with 64-bit Python but Wing itself runs as a 32-bit application.
On CentOS 64-bit systems, installing the libXtst.i386 and gtk2*386 packages with yum provides the necessary 32 bit support.
On Arch linux, the necessary packages are instead named lib32-glibc and lib32-gtk2.
|« 1.11. Installation Details and Options||Table of Contents||1.11.1. Installing Extra Documentation »|