Wt Installation

# Wt Installation instructions for Windows

This page lists the instructions for building and installing Wt on Windows. It is organized in 3 sections:

- Requirements
- Building and installing the library
- Trying the examples (or your own Wt application)

## Requirements

Wt for Windows uses the built-in web server connector or the ISAPI connector. The fastcgi connector is not supported. The built-in web server is more convenient during development and is easier to setup than the ISAPI connector. To use the built-in server, you have to link your projects against libwt and libwthttp. To use the ISAPI connector, you have to link to libwtisapi instead of libwthttp.

Requirements:

- Microsoft Visual Studio C++ 2005 or newer. Wt and its dependencies also build on the Express Edition, which is free (as in beer) to use.
- CMake cross-platform build system (www.cmake.org): cmake-2.6.x, Windows version (2.8 or newer recommended).
- Boost 1.36 (or later; a recent version is recommended)

Additional and optional requirements for some of the examples

- For https support: OpenSSL, version 0.9.8d or newer.
- To compress traffic: zlib 1.2.3
- Postgres, mysql, firebird client libraries for Dbo database backends
- Haru Free PDF Library, which is used to provide support for rendering PDF (WPdfImage, WPdfRenderer).
- GraphicsMagick, for supporting painting to raster images (PNG, GIF, ...) (WRasterImage).

We stronly recommend to use libraries which are all built using the same compiler and the same runtime configuration (/MT, /MD, /MTd or /MDd) to avoid incompatibilities with the C runtime libraries. Mixing CRTs is NOT recommended, the zlib DLL FAQ clearly explains why and what you should do about it (in short: use prebuilt libraries for the exact same compiler as you use, and if those are not available, rebuild the dependency libraries from the sources).

## Step by step instructions to build and install the Wt library

Up to date instructions are located on the Wt wiki page: Installing Wt on MS Windows Instructions on how to use the ISAPI connector for deployment under IIS are also available on the wiki page: ISAPI on Microsoft IIS

## Trying the examples (or your own Wt application) using wthttpd

#### 1. Run the example in the MSVC IDE

Right-click on the example project you want to run, and select 'Properties'. In Configuration Properties->Debugging, set the Command Arguments to

    --http-address=0.0.0.0 --http-port=8080 --deploy-path=/hello --docroot=.

This will start a httpd server listening on all local interfaces, on port 8080, and you may browse the example at http://127.0.0.1:8080/hello

Examples that need extra files to run, should be executed from their source directory in order to find their dependency files (icons, css files, etc. Watch for 404 errors in Wt's output). To do so, set the 'Working directory' for the example to wt-x.y.z/examples/ExampleName. Some examples (e.g. the wt home page) need the 'resources' directory to work correctly. Copy the wt-2.x.x/resources to the example's source directory to solve this problem. Other examples (such as the Charts example) may require the installation of ExtJs. See the Wt reference manual for more information on how to obtain and install ExtJs.

These are all the command-line options that are available (run the examples with --help to see the most recent list of available options):

    General options:
      -h [ --help ]              produce help message
      -t [ --threads ] arg (=10) number of threads
      --docroot arg              document root for static files
      --no-compression           do not compress dynamic text/html and text/plain
                                 responses
      --deploy-path arg (=/)     location for deployment

    HTTP server options:
      --http-address arg    IPv4 (e.g. 0.0.0.0) or IPv6 Address (e.g. 0::0)
      --http-port arg (=80) HTTP port (e.g. 80)

    HTTPS server options:
      --https-address arg     IPv4 (e.g. 0.0.0.0) or IPv6 Address (e.g. 0::0)
      --https-port arg (=443) HTTPS port (e.g. 443)
      --ssl-certificate arg   SSL server certificate chain file
                              e.g. "/etc/ssl/certs/vsign1.pem"
      --ssl-private-key arg   SSL server private key file
                              e.g. "/etc/ssl/private/company.pem"
      --ssl-tmp-dh arg        File for temporary Diffie-Hellman parameters
                              e.g. "/etc/ssl/dh512.pem"