To build Squish from source, you must begin by running configure to gather information on your system, such as the location of scripting language interpreters and toolkits.

All the configuration options are optional. However, if configure cannot find a component you want to use, you may need to use the command line options to provide it with the necessary information.


configure [options]

The square brackets indicate optional items and are not part of the syntax.


Three groups of options are supported:

  • disable
  • enable
  • with, which is used to set paths and filenames

The following table lists most of the available options. To see all options, run: configure -h.

By default, everything except debug is enabled, so you mostly need the --enable-* if you first use --disable-all to disable everything, and then use individual --enable-* options to enable anything you need. Most of the --enable-* and --disable-* options are used when doing split builds so that you only build the necessary parts at each stage.

The --with-* options are used to provide directories, dir, or filenames with full path, path, of components that configure failed to find, or where you want to ignore its findings in favor of your own choice. For example, if you are using the Qt toolkit, you might have two or more versions of Qt installed and want to tell configure which one you want Squish to use.

--disable-allDisables everything.
--disable-languageLanguage to disable: js (JavaScript), perl, python, ruby, or tcl.
--enable-64bitEnables Squish to test 64-bit applications. The --enable-debug option builds a debug version of Squish, which is usually not necessary.
--enable-allEnables everything.
--enable-languageLanguage to enable: js, perl, python, ruby, or tcl.
--with-java-home=dirDirectory where the Java Development Kit (JDK) is installed.
--with-pbsdk=dirDirectory where the PowerBuilder SDK is installed.
--with-perl=pathFilename with full path where the Perl interpreter (that is, the Perl executable) is installed.
--with-pydir=dirDirectory where Python is installed. Alternative to --with-python and --with-python3 options.
--with-python=pathFilename with full path where the Python interpreter (that is, the Python executable) is installed.
--with-python3=pathFilename with full path where the Python interpreter (that is, the Python executable) is installed.
--with-qtdir=dirDirectory where Qt is installed. In some (unusual) setups, Qt's library (.lib) files are in a non-standard location. In such cases, use the --with-qtimplibdir option to specify the appropriate directory.
--with-qtimplibdir=dirNon-standard location of Qt libraries.
--with-qtnamespace=namespaceNamespace that is used to wrap Qt library code in. This option is needed for Qt libraries configured using the -qtnamespace switch.
--with-ruby=pathFilename and full path where the the Ruby interpreter (that is, the Ruby executable) is installed.
--with-swtjar=pathFilename and full path where the Java/SWT .jar file is installed.
--with-tclconfig=dirDirectory where the Tcl file is installed.
--with-tkconfig=dirDirectory where the Tcl/Tk file is installed.

© 2023 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners.
The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.
Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.