|[Home] [Docs] [Users] [Gaming] [Crypto] [Devel] [Download] [Help]|
There are no fairdice enabled user or hosts apps. Dummy user and host apps are supplied with the development kit download, but they can only be used for testing the code and the protocol, not for playing actual games.
The development kit (client, server, dummy user, dummy host, test harness) has only been tested on cygwin (a unix emulator that runs under windows). If you don't use exactly the same set up, it many not compile, let alone run.
Windows Cygwin (including bash, make and gcc) Install Tom's Crypt Library (tested against v0.96): http://libtomcrypt.org/download.html (included in external module) Install the GNU Multiple Precision Arithmetic Library http://www.swox.com/gmp/ (included in external module) Install the Expat XML Parser Toolkit http://sourceforge.net/projects/expat/ (included in external module) Install SCEW http://www.nongnu.org/scew/ (included in external module) If you want to generate your own docs, you will also need Doxygen http://www.stack.nl/~dimitri/doxygen/ (included in external module)
1. sanity check the first section of the the MAKEFILE 2. type "make" 3. pray
This should give a long output to stdout (and a little to stderr).
Some of the tests require human scrutiny for verification (yes, this
ought to be changed. It is on the todo list). The actual tests are
in the tests/ subdirectory. If you get any fails, examine your
installs of the external applications, make sure you have all the
include and library files on the relevant paths. You may well need
to re-edit the make file and recompile. If you are unlucky you may
find yourself having to port the thread code.
Each one can be run either manually, by running each executable with the appropriate config file from a different bash shell or automatically by running a script which launches all the applications. Note that for timing purposes all the applications in a scenario should be launched within a second or two of each other. (yes, this is bad, please please come write a decent test harness for me.)
To run scenario single call the script
(You will probably find it easiest to add each of the scenario
specific bin directories to your path or use simlinks).
||the user log|
If the software runs without crashing but does the wrong thing (for instance, incorrectly verifies a usertext against a digest you have deliberately corrupted), please see the contact page for how to report the bug.