1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
6 <meta http-equiv="Content-Style-Type" content="text/css" />
7 <meta http-equiv="Content-type" content="text/html; charset=ISO-8859-1" />
8 <link rel="stylesheet" href="./runtime.css" type="text/css" />
9 <title>SILC Runtime Toolkit</title>
14 <table border="0" cellspacing="0" cellpadding="6" width="100%">
16 <td>Copyright © 2001 - 2008 SILC Project<br />
17 <a href="http://silcnet.org">SILC Project Website</a></td>
19 <a href="index.html">SILC Runtime Toolkit Manual</a><br />
20 <a href="masterindex.html">Index</a></small></td>
25 <div id="contentwrapper">
27 </div> <!-- navigation -->
30 <big><b>Building the Toolkit</b></big>
33 SILC Runtime Toolkit works on various platforms, such as on several Unix
34 systems and on Windows. Building of the Toolkit on some platform may
35 differ from the other. This document describes how to build the Toolkit
36 from the sources, to create linkable libraries and binaries, on all
37 platforms the Toolkit support.
40 The building instructions for all platforms are also included in the Toolkit
41 package. Please refer to the INSTALL file for general building instructions
42 for Unix systems, README.WIN32 for building on Windows systems,
43 README.MACOSX for building on Mac OS X, and README.SYMBIAN for building on
47 <ul class="toc_entries">
48 <li><a href="#unix">Building on Unix & Linux</a><br />
49 <li><a href="#windows">Building on Windows</a><br />
50 <li><a href="#macosx">Building on Mac OS X</a>
51 <li><a href="#symbian">Building on Symbian OS</a>
54 <b><a name="unix"></a>Building on Unix & Linux</b>
57 On Unix systems both statically and dynamically linkable libraries are
61 To build Toolkit on Unix systems, give commands:
70 On some systems you may need to give "gmake" command instead of "make". The
71 ./configure can take several options as arguments. To see them all give
75 <tt>./configure --help</tt>
78 The most important configuration options you may consider to use are:
81 <tt>--enable-debug</tt>
84 If you would like to enable the debugging for the compiled binaries
85 you can give this option to the `configure'. It is recommended to use
86 this option when you are doing development with Toolkit. It is helpful
87 to enable run-time debugging.
90 <tt>--with-iconv[=DIR]</tt>
93 If your system doesn't provide iconv() function in its native libraries
94 (usually libc) or if this function is broken (e.g. older Solaris systems),
95 you may want to use libiconv instead. The DIR is the upper path in your
96 system which contains lib/ and include/ for libiconv (e.g. /usr/local).
99 <tt>--without-pthreads</tt>
102 If you do not want to compile the programs with POSIX multi-threads support
103 you can give --without-pthreads option. This will disable the SILC Thread
104 API and SILC Mutex API. Furthermore if SILC Thread API is used when this
105 option is used, the routines work, but do not work in threads (are run
106 in the calling process and can block the process).
109 <tt>--disable-asm</tt>
112 If you have trouble compiling the assembler optimized code in the
113 package or does not want to use them, you can give the --disable-asm
114 option to the `configure' script. This will assure that assembler
115 optimized code is not compiled in.
118 <tt>--enable-ipv6</tt>
121 The `configure' will attempt to check for IPv6 support in your system.
122 However, if it fails, but you still want to compile in the IPv6 support
123 you can give --enable-ipv6 option to force the IPv6 support.
126 <tt>--disable-cpu-optimizations</tt>
129 By default the configure script will attempt to detect the type of your
130 CPU and enable any features specific to your CPU that could optimize the
131 performance of the Toolkit. If you are creating binary package that
132 should work on any CPU (and not only your CPU) you should diable these
133 optimizations. If you compile it for yourself only, keeping the
134 optimizations enabled is recommended.
137 After compilation you can install the Toolkit into your system by giving
141 <tt>make install</tt>
144 <br /> <br /> <br />
145 <b><a name="windows"></a>Building on Windows</b>
148 The Toolkit can be compiled several different ways on Windows. However,
149 this document describes the method to build the Toolkit to produce native
150 Win32 binaries. The Toolkit package can also be compiled on Cygwin and
151 MinGW. For these systems please refer to the README.WIN32 file in the
155 The Toolkit package includes ready MSVC++ Workspace files, that will
156 automatically compile the Toolkit. The MSVC++ workspace and project files
157 resides in the win32/ subdirectory of the Toolkit package. The `srt.dsw'
158 file is the workspace file that automatically supports compiling the Toolkit
159 and to generate the SILC Runtime DLL (libsrt.dll). You may also compile
160 debug version by selecteing the Debug compilation method.
162 <br /> <br /> <br />
163 <b><a name="macosx"></a>Building on Mac OS X</b>
166 Building the Toolkit on Mac OS X is almost identical on compiling on Unix
167 system. The reason for this is that the Mac OS X is Unix based operating
168 system. To build the Toolkit on Mac OS X, give the following commands:
172 setenv CFLAGS -no-cpp-precomp<br />
173 ./configure powerpc<br />
178 The ./configure can take several options as arguments. To see them all give
182 <tt>./configure --help</tt>
193 After compilation you can install the Toolkit into your system by giving
197 <tt>make install</tt>
199 <br /> <br /> <br />
200 <b><a name="symbian"></a>Building on Symbian OS</b>
203 The build environment for Symbian OS requires Carbide.c++ and MS Windows.
206 Download the freely available Carbide.c++ from Nokia at
207 <a href="http://forum.nokia.com">http://forum.nokia.com</a>. The exact
208 hyperlink location changes often, so it is not referenced here. It is
209 usually under "Tools and SDKs" link.
212 After installation a web browser is opened automatically by the
213 Carbide.c++ installer. Follow its instructions by installing the Perl,
214 CTags and the SDK. Perl and the SDK are required, but CTags is
215 optional and if necessary can be omitted.
218 The Toolkit is generic C and C++ code and should work with any
219 SDK. If you don't have SDK already installed, install the latest
220 version you can find. The links to SDKs are found in the Carbide.c++
221 instructions after installation. If you already have SDK in your
222 system, you should use that.
225 After installation import the Toolkit project to Carbide.c++ from the
226 symbian/ subdirectory in the Toolkit package.
229 Please read the README.SYMBIAN from the SILC Runtime Toolkit package for
230 complete building instructions.
233 </div> <!-- content -->
235 </div> <!-- contentwrapper -->
237 <table border="0" cellspacing="0" cellpadding="6" width="100%">
239 <td>Copyright © 2001 - 2008 SILC Project<br />
240 <a href="http://silcnet.org">SILC Project Website</a></td>
242 <a href="index.html">SILC Runtime Toolkit Manual</a><br />
243 <a href="masterindex.html">Index</a></small></td>