X-Git-Url: http://git.silcnet.org/gitweb/?p=runtime.git;a=blobdiff_plain;f=doc%2Fruntime.in%2Fbuilding.html;h=45ee00b12b060105ff5ba6839748f6efe8d3d4fa;hp=c3f5f5fec0c93889d9f429d2829d0f3c0ac2c3f3;hb=1ad1765203103b64292ace31d39503887e543b65;hpb=56cea60b47990096c4c2a16f57f7865f9708e361 diff --git a/doc/runtime.in/building.html b/doc/runtime.in/building.html index c3f5f5fe..45ee00b1 100644 --- a/doc/runtime.in/building.html +++ b/doc/runtime.in/building.html @@ -31,29 +31,31 @@ Building the Toolkit
 
-SILC Runtime Toolkit works on various platforms, such as on several Unix -systems and on Windows. Building of the Toolkit on some platform may -differ from the other. This document describes how to build the Toolkit -from the sources, to create linkable libraries and binaries, on all +SILC Runtime Toolkit works on various platforms, such as on several Unix +systems and on Windows. Building of the Toolkit on some platform may +differ from the other. This document describes how to build the Toolkit +from the sources, to create linkable libraries and binaries, on all platforms the Toolkit support.
 
The building instructions for all platforms are also included in the Toolkit package. Please refer to the INSTALL file for general building instructions -for Unix systems, README.WIN32 for building on Windows systems, and -README.MACOSX for building on Mac OS X. +for Unix systems, README.WIN32 for building on Windows systems, +README.MACOSX for building on Mac OS X, and README_SYMBIAN for building on +Symbian OS. +
-
 
+ -
 
 
Building on Unix & Linux
 
-On Unix systems both statically and dynamically linkable libraries are +On Unix systems both statically and dynamically linkable libraries are built by default.
 
@@ -125,11 +127,11 @@ you can give --enable-ipv6 option to force the IPv6 support. --disable-cpu-optimizations
 
-By default the configure script will attempt to detect the type of your -CPU and enable any features specific to your CPU that could optimize the -performance of the Toolkit. If you are creating binary package that -should work on any CPU (and not only your CPU) you should diable these -optimizations. If you compile it for yourself only, keeping the +By default the configure script will attempt to detect the type of your +CPU and enable any features specific to your CPU that could optimize the +performance of the Toolkit. If you are creating binary package that +should work on any CPU (and not only your CPU) you should diable these +optimizations. If you compile it for yourself only, keeping the optimizations enabled is recommended.
 
@@ -155,7 +157,7 @@ The Toolkit package includes ready MSVC++ Workspace files, that will automatically compile the Toolkit. The MSVC++ workspace and project files resides in the win32/ subdirectory of the Toolkit package. The `srt.dsw' file is the workspace file that automatically supports compiling the Toolkit -and to generate the SILC Runtime DLL (libsrt.dll). You may also compile +and to generate the SILC Runtime DLL (libsrt.dll). You may also compile debug version by selecteing the Debug compilation method.
 
 
@@ -225,9 +227,10 @@ After installation import the Toolkit project to Carbide.c++ from the symbian/ subdirectory in the Toolkit package.
 
-Please read the README.SYMBIAN from the SILC Runtime Toolkit package for +Please read the README.SYMBIAN from the SILC Runtime Toolkit package for complete building instructions. +
 
@@ -246,4 +249,3 @@ complete building instructions. -