View of /trunk/Video_Conferencing_Startup_Kit_Pkg_2/sipp/README.txt

    1 #  This program is free software; you can redistribute it and/or modify
    2 #  it under the terms of the GNU General Public License as published by
    3 #  the Free Software Foundation; either version 2 of the License, or
    4 #  (at your option) any later version.
    5 #
    6 #  This program is distributed in the hope that it will be useful,
    7 #  but WITHOUT ANY WARRANTY; without even the implied warranty of
    8 #  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    9 #  GNU General Public License for more details.
   10 #
   11 #  You should have received a copy of the GNU General Public License
   12 #  along with this program; if not, write to the Free Software
   13 #  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
   14 #
   15 #  Copyright (C) 2003,2004,2005,2006 - The Authors
   16 #
   17 
   18 BUILDING
   19 ********
   20 
   21 This is the Sipp package. Please refer to the http://sipp.sourceforge.net/
   22 WEB page for details and download of the last version.
   23 
   24 Normally, you should be able to build Sipp by just typing "make" in the
   25 current diractory. Then "sipp -h" will give you access to the online help.
   26 
   27 CONTRIBUTING
   28 ************
   29 
   30 Sipp is free software, under the terms of the GPL licence (please the the
   31 LICENCE.txt file for details). You can contribute to the development 
   32 of Sipp and contact us via Sourceforge to integrate your changes. If you 
   33 make changes in Sipp, *PLEASE* follow a few coding rules:
   34 
   35   - Use 80 columns code,
   36 
   37   - Do *NOT* use tabulations for indentation. Use spaces,
   38 
   39   - Please stay conform with the current indentation style (2 spaces
   40     indent, standard Emacs-like indentation). Examples:
   41 
   42     if (condition) {
   43       f();
   44     } else {
   45       g();
   46     }
   47 
   48   - Use "{" in if conditions even if there is only one instruction
   49     (see example above).
   50 
   51   - Do not use std C++ libs if something euivalent exists in libc
   52     (better portability). (e.g. prefer "printf" to "cout <<" ).
   53 
   54   - Check your changes can be compiled on:
   55  
   56       - Linux,
   57       - HPUX,
   58       - Tru64,
   59 
   60     (We can provide help on these portability points).
   61 
   62 Thanks,
   63 
   64   ojacques@users.sourceforge.net
   65   richard_gayraud@users.sourceforge.net
   66 
   67 ******************************************************************