Download

License and Pricing

Wt may be used using either an Open Source or a Commercial License.

If you wish to use the library using the GNU General Public License (GPL), you may build a web application with Wt and deploy it, but per the terms of the GPL, you are obliged to make the source code available to anyone who you give the application to install the application on its own server. This also applies to redistribution of the Wt library, in original or modified form.

The Commercial License has no such limitations: you may redistribute applications developed with Wt without needing to redistribute the source code. The license is a royalty-free, perpetual license for one developer to use the API of Wt (respectively Wt::Dbo) for application development, using the latest version of Wt or any version released during one year.

Available packages

If you are on Ubuntu, you can install a reasonably recent version of Wt from Pau Garcia's PPA repository:

$ sudo add-apt-repository ppa:pgquiles/wt
$ sudo apt-get update
$ sudo apt-get install witty witty-dev witty-doc witty-examples

The last package (witty-examples) installs the examples in /usr/lib/Wt/examples. You can run each of them like this:

$ /usr/lib/Wt/examples/hello/hello

Older releases are still available at sourceforge.net.

The Wt installer: winst

This requires CMake and GNU make and will try to download software using wget.

Download the package (winst-0.4.tar.gz) or get the latest git version:

$ git clone http://www.webtoolkit.eu/git/winst.git

System requirements

• CMake cross-platform make configure utility.
  CMake >= 2.6 is preferred (although by the act of a miracle, 2.4 still works).
• The indispensable boost C++ library: boost-1.41 or later. Older boost versions (up to 1.36) may also be used, but some functionality will be missing (JSON parsing and a better SQL query parsing for Wt::Dbo).
  The following boost libraries (which are not headers only) are needed: boost_date_time, boost_regex, boost_program_options, boost_signals, boost_system, and optionally (but highly recommended) boost_thread.

• OpenSSL: if available, then the HTTPS protocol will be supported by the web client (Http::Client) and web server (wthttp connector), an additional cryptographic hash function added to the Auth library (Auth::SHA1HashFunction), and WebSockets (fully) supported by web server.
• libharu: if available, a WPdfImage paint device will be included, which outputs to PDF. For more complete support for TrueType fonts and Unicode, you need a patched libharu.
• GraphicsMagick: if available, a WRasterImage paint device will be included, which outputs to raster images like PNG or GIF.
• pango (LGPL): if available, text rendering for WPdfImage and WRasterImage will be assisted by this library for TrueType font selection, taking into consideration both the font face and unicode coverage.
• PostgreSQL: if available, a postgres connector for the ORM library (Wt::Dbo) will be built.

The other requirements depend on the connector support you would like. The connector is what makes your Wt application communicate with the browser:

For FastCGI (Unix only):

• Apache 1 or 2, or another web server which supports the FastCGI protocol.
• FastCGI development kit : fcgi-2.4.0
• When using apache: Apache mod_fastcgi: mod_fastcgi-2.4.x.
  Alternatively you may use mod_fcgid: mod_fcgid-2.3.5.

For the built-in http deamon, wthttpd:

• Optionally, libz (for compression-over-HTTP) and openssl (for HTTPS support).

For ISAPI (Win32 only):

• The ISAPI connector only works for deploying Wt applications withing a Microsoft IIS server.

Git repository

If you want to keep track of the latest changes, or participate in Wt development, you may want to work from the github repository.

Alternatively checkout the repository using:

$ git clone http://www.webtoolkit.eu/git/wt.git