Distributing and Sharing an Installation

Once you have completed the build steps described in Installing Squish for Qt from Desktop Source Packages or Installing Squish for Qt from Embedded Source Packages, you have a system ready to use on the local machine, located in <SQUISHDIR>. This entire directory with subfolders can be zipped up into an archive and extracted elsewhere.

This section is for users or system administrators who wish to distribute or share a build performed on one machine to a different location or for users on other machines.

There are many reasons why you might want to reuse the built executables and libraries:

• Division of labor between developers or system administrators who will build Squish and testers who will use Squish.
• Separation between machines used for product development and machines used specifically for testing.
• Reduced maintenance work required when upgrading the software.
• Saving time by doing a single compilation and distributing the results.
• Saving disk space since only the executables and their supporting libraries need to be distributed, not the entire source code.

Configuring the installation

After unzipping the archive on another system, there are .ini files with paths that may need to be fixed up before you can use the installation. Some of these settings are stored under <SQUISHDIR>/etc and others are stored in the Squish User Settings Directory.

The squishconfig command can be used to fix up the paths in Squish .ini files. The exact commands you need depend on various things, such as which edition of Squish you are using, or whether you are using a non-default installation of python. Some examples are below.

Configuring Squish for Qt

On macOS, Squish needs to know the path to Qt Libraries.

$ squishconfig --qt /path/to/QtCore.framework

On other platforms, this step is not necessary

Configuring for a non-default Python

By default, Squish uses the Python from the archive. This version of Python has some hardcoded paths in it which can make pip unusable. To use a different Python installation:

$ squishconfig --python /path/to/python

Configuring Squish for Java

Squish for Java needs to know where the Java interpreter is, and this is not set from the IDE.

$ squishconfig --java /path/to/java