Chapter 3. How to Install Squish

Table of Contents

3.1. Installing the Command Line Tools, Server, and Classic IDE
3.1.1. Installing from Binary Packages
3.1.2. Installing from Source Packages
3.1.3. Distributing and Sharing an Installation
3.1.4. Installation for Mac OS X
3.1.5. Installation for Maemo
3.2. Installing the New IDE
3.2.1. Installing the New IDE on Windows
3.2.2. Installing the New IDE on Linux
3.2.3. Installing the New IDE on Mac OS X
3.2.4. Using Squish

This chapter explains how to install Squish on Windows, and on Unix-like systems such as Linux, Mac OS X, and Embedded Linux. Squish 4 is supplied as two separate packages. The first package (Squish Tools) is just like the original Squish 3 package and contains the command line tools, the squishserver, and the Classic IDE. This package is installed just the same as for Squish 3. (Keep in mind that Squish 4 automatically binds to AUT classes so if you needed to install from source for Squish 3, you might not have to for Squish 4.) The second package (Squish IDE) contains the New IDE—this is always supplied as a binary package so it is very easy to install.

In many cases Squish's command line tools can be successfully installed using binary packages, but there are some situations where it is necessary to build it from source, either using a standard build or—in particular cases—a non-standard build.

The cases where it is not possible to do a standard build are when you want to test applications built with the Qt 3.x library—except for Qt 3.3.5 and Qt 3.3.6 for which binary packages are available—the Qt/Embedded 2.3 library, or with any Qt library that is single threaded or that has been statically built. If any of these applies, the following sections describe how to do a non-standard build of Squish from source in the relevant circumstances:

If none of the cases above applies—for example, you are testing Java or Web applications or native Mac OS X or Windows applications, or Qt 4 applications using a standard (multi-threaded and shared) library, then using a binary package is the quickest and easiest way to get Squish up and running. The process is explained in Installing from Binary Packages (Section 3.1.1).

[Note]Using Squish with Qt debug libraries

The prebuilt binary packages are built against release versions of the Qt libraries—not against the debug versions. If you want to use Squish with Qt debug libraries you will need to build Squish from source. (See Installation for Testing Pure Qt 4 Applications (Section 3.1.2.2).)

However, if for some reason—perhaps you are using an unusual Unix system or setup, or if you want to use Qt debug libraries—a binary package is not suitable, you can always do a standard build from source. This is explained in the section Installing from Source Packages (Section 3.1.2), although it is also worth reading Configure Switches (Section 3.1.2.1.1) first, so that you know what options are available to you when you run configure.

And if you want to use a Squish installation on more than one machine, you will find it helpful to read Distributing and Sharing an Installation (Section 3.1.3).

Finally, remember that once the command line tools package has been successfully installed, go on to install the the New IDE (Installing the New IDE (Section 3.2)). Installation is easy and the New IDE provides more functionality and is more convenient to use than the Classic IDE.