Symptoms¶
You built Squish from sources and copied the build to another computer. However, the Squish IDE does not alow you to choose this Squish build.
While trying to analyse the problem you try to run <SQUISH_DIR>\bin\squishrunner.exe (Squish IDE starts that tool as the first step to determine the version of that Squish installation) and you are getting the following error message:
_squishrunner - Application Error
(X) The application was unable to start correctly (0xc0000013). Click OK to
close the application. \[OK\]
Known cause - Missing changes in paths.ini/Qt libraries¶
Squish uses Qt as well, so the Qt libraries must be made available to it.
Solution #1 - Include Qt shared libraries¶
The most portable solution is to package Qt as recommended by the vendor of Qt with the Squish source build. In the simplest case, it consists of this step:
For Qt 4.x:
Copy the Qt Core and Qt Gui shared libraries...
QtCore4.dll
QtGui4.dll
...into the folder SQUISH_DIR/bin folder.
For Qt 5.x:
Copy the Qt Core and Qt Gui shared libraries...
Qt5Core.dll
Qt5Gui.dll
...into the folder SQUISH_DIR/bin folder.
Solution #2 - Adjust squish_dir/etc/paths.ini¶
Squish automatically looks for them in the "LibraryPath" specified in the file <SQUISH_DIR>/etc/paths.ini, so this is something that you could adjust when copying the build to another computer.
Here is an example entry:
# Automatically generated by configure. Will be overwritten on next run.
[Paths]
LibraryPath = "@(SQUISH_PREFIX)\\bin;C:\\QT\\bin;C:\\Python25"If the other computer has Qt in C:\Users\myuser\Qt, then the adjusted contents would look like this:
# Automatically generated by configure. Will be overwritten on next run.
[Paths]
LibraryPath = "@(SQUISH_PREFIX)\\bin;C:\\Users\\myuser\\Qt\\bin;C:\\Python25"Note that the path to the Python installation is also something that must be adjusted.