silc/
- Includes SILC client. There can be some extra files that will
- never appear in public distribution, such as, configuration files.
+ Includes an example implementation of ncurses based SILC client.
+ It won't compile with current Toolkit since it is not being
+ updated. It is still good example for Toolkit programmer to
+ figure out how to use SILC Toolkit.
+
+ silcer/
+
+ Includes an example implementation of GUI (Gnome) base SILC
+ client. Please read silcer/README for more information.
silcd/
Includes SILC server. There can be some extra files that will
never appear in public distribution, such as, configuration files.
+ win32/
+
+ Includes win32 Toolkit specific files. It includes MSVC++
+ Workspace files. The win32/tests includes example code for
+ use of SILC Toolkit and SILC Client Library on Win32 GUI
+ application.
+
Howto Compile SILC Source Tree
==============================
by both cilent and server is very heavy, thus it is common to test
the programs as follows:
- ./silc -d -f configfile 2>log
- ./silcd -d -f configfile 2>log
+ ./silc -d "*" -f configfile 2>log
+ ./silcd -d "*" -f configfile 2>log
-Do not give the -d options if you do not want to dump the debugging.
+The -d option enables the debug printing. The argument for the -d option
+is a string that is used to match the output debug. The example "*" will
+match for everything, and all debugs will be printed. If you want to
+limit the debugs you want to printout you can give for example a string
+like "*server*,*rng*" to match all functions, and filenames that has
+"server" or "rng" string in them. Others will not be printed out. You
+can freely define regural expressions as debug string.
Howto Clean SILC Source Tree