@@ -24,53 +24,26 @@ <h2>Requirements</h2>
2424
2525< p > Requirements:
2626< ul >
27- < li > Microsoft Visual Studio C++ 2005. Wt and all its dependencies also
28- build on the Express Edition, which is free (as in beer) to use. If you
29- use the Express Edition, you will also need to install the Platform
30- SDK, which can be downloaded from Microsoft. It is recommended to
31- upgrade your MSVC 2005 with Service Pack 1 as it contains important
32- bugfixes. We have not tested Wt on older versions of MSVC.</ li >
33- < li > CMake cross-platform build system (www.cmake.org): cmake-2.4.x,
27+ < li > Microsoft Visual Studio C++ 2008. Wt and its dependencies also
28+ build on the Express Edition, which is free (as in beer) to use.
29+ < li > CMake cross-platform build system (www.cmake.org): cmake-2.6.x,
3430 Windows version.</ li >
3531 < li > Boost 1.35 (or later).</ li >
36- < li > Xerces-C++ XML parser, version 2.7.0 or newer.</ li >
37- < li > OpenSSL, version 0.9.8d or newer.</ li >
38- < li > zlib 1.2.3</ li >
3932</ ul >
4033</ p >
4134
4235< p > Additional and optional requirements for some of the examples
4336< ul >
37+ < li > For https support: OpenSSL, version 0.9.8d or newer.</ li >
38+ < li > To compress traffic: zlib 1.2.3</ li >
4439< li > libgd (style, wt-homepage, mandelbrot)</ li >
4540< li > libmysql and libmysql++-2.x (hangman)</ li >
4641</ ul >
4742</ p >
4843
49- < p > On unix systems, libraries are usually installed in standard locations,
50- with their header files in /usr/include (or variants) and the libraries in
51- /usr/lib (or variants). Windows does not have such standard locations for
52- storing header files and libraries. Therefore, you will have to point out
53- where the libraries can be found. If you follow the recommendations below,
54- the task of specifying these paths will be require minimal effort (but
55- you'll still have to ensure that the executable will be able to locate the
56- DLLs at runtime, e.g. by adding the directories to PATH).
57- </ p >
58-
59- < p > CMake will automatically locate your libraries in subdirectories of
60- USERLIB_ROOT (defaults to c:/libraries). Use the following directories:
61- < ul >
62- < li > Boost: During configuration of Boost, set the prefix to $USERLIB_ROOT/Boost</ li >
63- < li > Xerces-C++: TBD</ li >
64- < li > OpenSSL: TBD</ li >
65- < li > zlib: TBD</ li >
66- < li > libgd: TBD</ li >
67- < li > libmysql: TBD</ li >
68- < li > libmysql++: TBD</ li >
69- </ ul >
70-
7144< p >
7245We stronly recommend to use libraries which are all built using the same
73- compiler (MSVC 2005 SP1) and the same runtime configuration (/MT, /MD, /MTd
46+ compiler and the same runtime configuration (/MT, /MD, /MTd
7447or /MDd) to avoid incompatibilities with the C runtime libraries. Mixing
7548CRTs is NOT recommended, the < a href ="http://www.zlib.net/DLL_FAQ.txt "> zlib
7649DLL FAQ</ a > clearly explains why and what you should do about it (in
@@ -80,69 +53,37 @@ <h2>Requirements</h2>
8053
8154< hr />
8255
83- < h2 > Building and installing the Wt library</ h2 >
84-
85- < h4 > 1. Run CMake</ h4 >
86-
87- < p > In the CMake GUI, set the 'Where is your source code' to the location where
88- you unpacked the source code. Set 'Where to build the binaries' to a build
89- directory (can be the same as the location of the source code). Press
90- 'Configure' and choose 'Build For Visual Studio 8 2005'.</ p >
91-
92- < p > During configuration, you will see messages that confirm that fastcgi is
93- disabled, and that wthttp is enabled. You will probably also receive
94- notifications of dependencies that were not found. You can now manually
95- adjust the paths to the dependencies and other configuration parameters,
96- and press the 'Configure' button again. When your configuration is complete,
97- press 'Ok' and a solution file will be generated.</ p >
98-
99-
100- < p > Some variables you may want to change are:</ p >
101-
102- < dl >
103- < dt > < strong > CMAKE_INSTALL_PREFIX</ strong > </ dt >
104- < dd > Installation prefix for the library and include files)</ dd >
105- < dt > < strong > CONFIGURATION</ strong > </ dt >
106- < dd > Location of the configuration file</ dd >
107- </ dl >
56+ < h2 > Step by step instructions to build and install the Wt library</ h2 >
10857
109- < h4 > 2. Build the library and the examples</ h4 >
58+ Up to date instructions are located on the Wt wiki page:
59+ < a href ="http://www.webtoolkit.eu/wt/wiki/index.php/Installing_Wt_2.1_on_MS_Windows "> Installing Wt on MS Windows</ a >
11060
111- Start Microsoft Visual Studio, open the generated solution file, and
112- select Build-> Build Solution (or hit F7).
61+ < h2 > Trying the examples (or your own Wt application) using wthttpd</ h3 >
11362
114- < h4 > 3. Install the library:</ h4 >
115-
116- No installation is required for wt applications, as long as the application
117- is able to locate its dependencies (.dll files). Add the directories to the
118- dependencies to the PATH, copy them to the current directory, or to any other
119- location where Windows looks for dll files.
120-
121- < hr />
122-
123- < h2 > Trying the examples (or your own Wt application)</ h2 >
124-
125- < h3 > Using wthttpd</ h3 >
126-
127- < h4 > 1. Run the example < i > X</ i > </ h4 > in the MSVC IDE
63+ < h4 > 1. Run the example in the MSVC IDE </ h4 >
12864
12965Right-click on the example project you want to run, and select 'Properties'.
13066In Configuration Properties-> Debugging, set the Command Arguments to
13167< pre >
13268--http-address=0.0.0.0 --http-port=8080 --deploy-path=/hello --docroot=.
13369</ pre >
134- The easiest way to locate the dependency dlls, is to append their location
135- to the PATH variable. In order to do so, change the Environment field to
136- contain a PATH directive:
137- < pre >
138- PATH=c:/libraries/lib;c:/Boost/lib;<path to wt.dll>;<path to wthttp.dll>
139- </ pre >
14070
14171< p >
14272This will start a httpd server listening on all local interfaces, on
14373port 8080, and you may browse the example at < a
14474href ="http://127.0.0.1:8080/hello "> http://127.0.0.1:8080/hello</ a > </ p >
14575
76+ < p >
77+ Examples that need extra files to run, should be executed from their source
78+ directory in order to find their dependency files (icons, css files, etc.
79+ Watch for 404 errors in Wt's output). To do so, set the 'Working directory'
80+ for the example to wt-2.x.x/examples/ExampleName. Some examples (e.g. the
81+ wt home page) need the 'resources' directory to work correctly. Copy
82+ the wt-2.x.x/resources to the example's source directory to solve this
83+ problem. Other examples (such as the Charts example) may require the
84+ installation of ExtJs. See the Wt reference manual for more information
85+ on how to obtain and install ExtJs.
86+
14687< p >
14788These are all the command-line options that are available:
14889< pre >
0 commit comments