readme.txt               first revision       by gfoot        14/01/98
______________________________________________________________________

                            |o|   _  _ . 
                            |||-.| |/_)|-
                            '''-'' '`- `-  0.9.12

    libnet is (c) Copyright Chad Catlett and George Foot 1997-1998
______________________________________________________________________


This is a file you should read in full before doing anything else.



0. Contents
~~~~~~~~~~~
   0 - Contents
   1 - Disclaimer
   2 - Distribution conditions
   3 - Directory structure
   4 - Installation
   5 - Uninstallation
   6 - Usage instructions
   7 - Contacting the authors



1. Disclaimer
~~~~~~~~~~~~~
   This library is provided free of charge without warranty. The
   authors hereby disclaim all liability for any damage use or
   abuse of this library may cause, directly or indirectly, to
   anything at all. You use this at your own risk.



2. Distribution conditions
~~~~~~~~~~~~~~~~~~~~~~~~~~
   libnet is swap-ware. You may use, modify, redistribute, and
   generally hack it about in any way you like, but if you do
   you must send the authors something in exchange. This could
   be a complimentary copy of a game, an addition or improvement
   to libnet, a bug report, some money (this is particularly
   encouraged if you use libnet in a commercial product), or
   just an email saying `Hi!'. If you redistribute parts of
   libnet, or make a game using it, it would be nice if you
   mentioned libnet in the credits, but if you just want to
   pinch a few drivers or techniques that's fine.

   However, please do not distribute modified copies under the
   name `libnet' without stating clearly that they have been
   modified.



3. Directory structure
~~~~~~~~~~~~~~~~~~~~~~
   When you unzipped this you should have told your unzip
   program to recreate the directory structure (e.g. by passing
   the `-d' switch to PKUNZIP; WinZip and InfoZIP do it
   automatically). If not, you'll have to delete it and start
   again.

   Having unzipped the library properly, you should have a
   directory called `libnet' with the following subdirectories:

    docs        -   documentation
    include     -   include files
    examples    -   example programs
    tests       -   miscellaneous test programs
    core        -   core library code
    drivers     -   driver code
    lib	        -   library destination



4. Installation
~~~~~~~~~~~~~~~
   To install libnet, simply run `make' from its base directory
   (the one with `makefile' in it). This will compile
   everything, copy the library file and include file to your
   djgpp directory tree, and build the example programs.

   After installation, you can remove intermediate files by
   typing `make clean' from that same directory.

   If something goes badly wrong and you need to rebuild the
   library from scratch, run `make rebuild'.



5. Uninstallation
~~~~~~~~~~~~~~~~~
   To completely uninstall the library, run `make veryclean'.
   This will remove all object code and executables, and it will
   delete the library libnet.a and header file libnet.h from
   your djgpp `lib' and `include' directories respectively.



6. Usage instructions
~~~~~~~~~~~~~~~~~~~~~
   To use the library in your programs, you must:

   - #include <libnet.h> in your source files that need it. You
     don't need to do this in files that don't call libnet
     routines and don't use libnet structures.

   - Link the libnet.a file into your executables. You can
     either pass it to the linker like a normal object file, or
     just put `-lnet' at the end of the linker command line (the
     one that generates the executable file).


   See the docs directory for details of what the functions do,
   or the example programs for further guidance.



7. Contacting the authors
~~~~~~~~~~~~~~~~~~~~~~~~~
   Main authors' email addresses:

      George Foot (gfoot): george.foot@merton.oxford.ac.uk
      Chad Catlett (dwi): dwi@netc.com


   For queries about specific drivers, please see the
   documentation for the driver in question.

