First apply the instructions in Section 2.2, “General Instructions” without actually executing the ./build script, then at the command line type as follows:

Qt will generate the Makefiles for the Qtc wrapper libraries.

This will build the libraries - this may take some time. (Type gmake all to build the both the release and debug versions of the Qtc libraries, if required).

Enter the superuser password

The Qtc libraries are now installed

The Haskell package (qt) is built with Cabal as follows:

This will compile all the Haskell code which may take some time.

Enter the superuser password

To compile the qtHaskell programs in the examples and demos directories type:

The qtHaskell version of Glome is built as a package (qt-glome) with Cabal as follows:

This will compile all the Haskell code for Glome which may take some time.

Enter the superuser password

To compile the imageviewer demo program for Glome type:

(See the section Section 3.1, “Building qtHaskell Applications” for instructions on how to build individual qtHaskell programs).

N.B. The Windows manual installation procedure for qtHaskell version 1.1.10 requires an MSYS bourne shell interpreter as well as the MinGW toolset. If necessary this should be installed, then open an MSYS window and cd to the current build location. During the installation process some commands will be typed at the MSYS prompt and some will be typed at the Dos box prompt.

Open a Dos box and apply the instructions in Section 2.2, “General Instructions” without actually executing the build batch file.

Add the installation bin directories to the local path environment variable.

Edit the file qt.cabal and add the line

where mypath is the full pathname of the installation directory e.g. c:\qthaskell\qthaskell-1.1.10.

This will build the libraries - which may take some time. (Type mingw32-make all to build both the release and debug versions of the Qtc libraries, if required).

The Haskell package (qt) is built with Cabal as follows:

Then at the MSYS window type

This will compile all the Haskell code which may take some time. It is also likely that mingw32-make will crash when it actually tries to link the archive. Ignore that and carry on back at the Dos box as follows.

This will link the library and install it as a Haskell package.

N.B. The library linking will take a very, very long time if left to run to its normal completion. The following procedure, although somewhat unorthodox may reduce the link time from several hours to a few minutes.

After you have typed the runhaskell Setup.hs build command, monitor the state of the dist/build directory in the current installation directory (e.g. type ls -l dist/build in the MSYS window. Once the ar program has completed building the libHSqt-1.1.10.a library (its final size is normally about 95MB), it will start to build the HSqt-1.1.10.o file, which may take several hours as opposed to a few minutes for the library. You can check that the HSqt-1.1.10.o file is being built by looking to see whether the ld program is running in the system process monitor. If so simply terminate the runhaskell Setup.hs build command and continue with the runhaskell Setup.hs install command.

N.B. the install command requires that a file named HSqt-1.1.10.o actually exists on the disk in the dist/build directory, even if its size is 0 bytes. If you only have a HSqt-1.1.10.o.tmp file when you terminate the build command, move it to HSqt-1.1.10.o before running the install command.

To compile the qtHaskell programs in the examples and demos directories type:

The qtHaskell version of Glome is built as a package (qt-glome) with Cabal as follows:

This will compile and install all the Haskell code for Glome which may take some time.

To compile the imageviewer demo program for Glome type:

(See the section Section 3.1, “Building qtHaskell Applications” for instructions on how to build individual qtHaskell programs).

Finally don't forget to add the installation bin directory to the path environment variable using the Windows control panel.