remove jrtp (we can always pull it out of the archives)

git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@1035 d0543943-73ff-0310-b7d9-9358b9ac24b2

libs/jrtplib/.in

-/* .in.  Generated from configure.in by autoheader.  */
-
-/* Define to 1 if you have the <dlfcn.h> header file. */
-#undef HAVE_DLFCN_H
-
-/* Define to 1 if you have the <inttypes.h> header file. */
-#undef HAVE_INTTYPES_H
-
-/* Define to 1 if you have the <memory.h> header file. */
-#undef HAVE_MEMORY_H
-
-/* Define to 1 if you have the <stdint.h> header file. */
-#undef HAVE_STDINT_H
-
-/* Define to 1 if you have the <stdlib.h> header file. */
-#undef HAVE_STDLIB_H
-
-/* Define to 1 if you have the <strings.h> header file. */
-#undef HAVE_STRINGS_H
-
-/* Define to 1 if you have the <string.h> header file. */
-#undef HAVE_STRING_H
-
-/* Define to 1 if you have the <sys/stat.h> header file. */
-#undef HAVE_SYS_STAT_H
-
-/* Define to 1 if you have the <sys/types.h> header file. */
-#undef HAVE_SYS_TYPES_H
-
-/* Define to 1 if you have the <unistd.h> header file. */
-#undef HAVE_UNISTD_H
-
-/* Name of package */
-#undef PACKAGE
-
-/* Define to the address where bug reports for this package should be sent. */
-#undef PACKAGE_BUGREPORT
-
-/* Define to the full name of this package. */
-#undef PACKAGE_NAME
-
-/* Define to the full name and version of this package. */
-#undef PACKAGE_STRING
-
-/* Define to the one symbol short name of this package. */
-#undef PACKAGE_TARNAME
-
-/* Define to the version of this package. */
-#undef PACKAGE_VERSION
-
-/* Define to 1 if you have the ANSI C header files. */
-#undef STDC_HEADERS
-
-/* Version number of package */
-#undef VERSION
-
-/* Define to 1 if your processor stores words with the most significant byte
-   first (like Motorola and SPARC, unlike Intel and VAX). */
-#undef WORDS_BIGENDIAN

libs/jrtplib/AUTHORS

-

libs/jrtplib/INSTALL

-Installation Instructions
-*************************
-
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
-
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-
-Basic Installation
-==================
-
-These are generic installation instructions.
-
-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
-
-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-
-The simplest way to compile this package is:
-
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.  If you're
-     using `csh' on an old version of System V, you might need to type
-     `sh ./configure' instead to prevent `csh' from trying to execute
-     `configure' itself.
-
-     Running `configure' takes awhile.  While running, it prints some
-     messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.
-
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-Compilers and Options
-=====================
-
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about.  Run `./configure --help' for
-details on some of the pertinent environment variables.
-
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
-   If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory.  After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
-By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc.  You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
-
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS KERNEL-OS
-
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script).  Here is a another example:
-
-     /bin/bash ./configure CONFIG_SHELL=/bin/bash
-
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
-

libs/jrtplib/LICENSE.MIT

-
-Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the "Software"),
-to deal in the Software without restriction, including without limitation
-the rights to use, copy, modify, merge, publish, distribute, sublicense,
-and/or sell copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
-THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
-IN THE SOFTWARE.
-

libs/jrtplib/Makefile.am

-SUBDIRS = src 
-EXTRA_DIST = LICENSE.MIT ChangeLog README.TXT jrtplib.dsw jrtplib.dsp jrtplib.vcproj \
-	     jrtplib.sln jrtplib_wce.vcproj jrtplib_wce.sln
-
-if IS64BITLINUX
-AM_CFLAGS = -m64 -march=k8 -fPIC
-endif
-
-dist-hook: distclean
-	rm -f $(distdir)/src/rtpconfig_unix.h
-	rm -f $(distdir)/src/rtptypes_unix.h
-	mv $(distdir)/jrtplib.dsw $(distdir)/jrtplib.dsw.tmp
-	mv $(distdir)/jrtplib.dsp $(distdir)/jrtplib.dsp.tmp
-	todos < $(distdir)/jrtplib.dsw.tmp > $(distdir)/jrtplib.dsw
-	todos < $(distdir)/jrtplib.dsp.tmp > $(distdir)/jrtplib.dsp
-	rm $(distdir)/jrtplib.dsw.tmp
-	rm $(distdir)/jrtplib.dsp.tmp
-	chmod a-x $(distdir)/jrtplib.vcproj
-	chmod a-x $(distdir)/jrtplib.sln
-	chmod a-x $(distdir)/jrtplib_wce.vcproj
-	chmod a-x $(distdir)/jrtplib_wce.sln

libs/jrtplib/NEWS

-

libs/jrtplib/README

-

libs/jrtplib/README.TXT

-------------------------------------------------------------------------------
-                                                                March 26, 2006
-
-
-                                   JRTPLIB (v3.5.2)
-
-
-                      Developed at the The Expertise Centre for 
-                      Digital Media (EDM), a research institute  
-                              of the Hasselt University
-
-                             http://www.edm.uhasselt.be/
-                               http://www.uhasselt.be/
-
-
-LIBRARY LOCATION AND CONTACT
-============================
-
-Normally, you should be able to download the latest version of the library
-from this url:
-	http://research.edm.uhasselt.be/jori/jrtplib/jrtplib.html
-
-If you have questions about the library, you can mail me at:
-	jori@lumumba.uhasselt.be
-	
-There is also a mailing list for the library. To subscribe to the list, 
-send an e-mail with the text 'subscribe jrtplib' as the message body (not 
-the subject) to majordomo@edm.uhasselt.be and you'll receive further 
-instructions.
-
-ACKNOWLEDGMENT
-==============
-
-I would like thank the people at the Expertise Centre for Digital Media
-for giving me the opportunity to create this rewrite of the library.
-
-DISCLAIMER & COPYRIGHT
-======================
-
-Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the "Software"),
-to deal in the Software without restriction, including without limitation
-the rights to use, copy, modify, merge, publish, distribute, sublicense,
-and/or sell copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
-THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
-IN THE SOFTWARE.
-
-INSTALLATION NOTES
-==================
-
-* To compile the library on a unix-like platform, just start the configure
-  script. This should generate a makefile which you can use to start
-  building the library using 'make'.
-
-* To compile the library on an MS-Windows platfrom: Visual Studio
-  workspace files are included. The project will search
-  for JThread files in ..\jthread-1.1.2
-  To compile the library without using JThread, comment the line
-  with RTP_SUPPORT_THREAD in rtpconfig_win.h
-  Note that for Visual Studio 6, you must have service pack 6 for 
-  installed to be able to compile the library.  (NOTE:  In this copy
-  of the lib, jthread has been included and does not need to be included
-  seperately)
-
-* For a manual about the library, please refer to doc/ subdirectory.
-  Using 'make doc', a PDF version of the documentation will be built.
-  Note that you'll need to have the pdflatex LaTeX compiler installed.
-  Alternatively, you can download the documentation from the homepage:
-  http://research.edm.uhasselt.be/jori/jrtplib/jrtplib.pdf
-
-* For systems with low memory or for applications which will involve only
-  a few participants at a time:
-  You can set the HASHSIZE defines in rtpsources.h, rtpudpv4transmitter.h
-  and rtpudpv6transmitter.h to a lower value to avoid memory being wasted.
-  Note that the library will have to be recompiled.
-
-* Used defines:
-	- WIN32:
-		For compilation on an Win32 platform.
-	- _WIN32_WCE:
-		Define needed for compilation on a WinCE platform
-	- RTP_HAVE_SYS_FILIO:
-		Set if <sys/filio.h> exists.
-	- RTP_HAVE_SYS_SOCKIO:
-		Set if <sys/sockio.h> exists.
-	- RTP_BIG_ENDIAN:
-		If set, assume big-endian byte ordering.
-	- RTP_SOCKLENTYPE_UINT:
-		Indicates that getsockname used an unsigned int as its
-		third parameter.
-	- RTP_HAVE_SOCKADDR_LEN:
-		Indicates that struct sockaddr has an sa_len field.
-	- RTP_SUPPORT_IPV4MULTICAST:
-		Enables support for IPv4 multicasting.
-	- RTP_SUPPORT_THREAD:
-		Enables support for JThread.
-	- RTP_SUPPORT_SDESPRIV:
-		Enables support for RTCP SDES private items.
-	- RTP_SUPPORT_PROBATION:
-		If set, a few consecutive RTP packets are needed to validate
-		a member.
-	- RTP_SUPPORT_GNUDRAND:
-		If set, the RTPRandom class will use drand48_r and srand48_r
-	- RTP_SUPPORT_RANDR:
-		If set and RTP_SUPPORT_GNUDRAND is not set, the RTPRandom
-		class will use rand_r.
-	- RTP_SUPPORT_GETLOGINR:
-		If set, the library will use getlogin_r instead of getlogin.
-	- RTP_SUPPORT_IPV6:
-		If set, IPv6 support is enabled.
-	- RTP_SUPPORT_IPV6MULTICAST:
-		If set, IPv6 multicasting support is enabled.
-	- RTPDEBUG:
-		Enables some memory tracking functions and some debug routines.
-	
-------------------------------------------------------------------------------
-

libs/jrtplib/doc/Makefile.am

-EXTRA_DIST = jrtplib.tex manual.tex
-
-doc: jrtplib.pdf
-	
-jrtplib.pdf: jrtplib.tex
-	pdflatex jrtplib.tex
-	pdflatex jrtplib.tex
-
-clean:
-	rm -f jrtplib.{toc,aux,log,pdf}

libs/jrtplib/doc/manual.tex

-\documentclass[a4paper,12pt]{article}
-\usepackage{listings}
-\lstset{language=C++}
-\lstset{tabsize=4}
-\begin{document}
-	\title{JThread manual (v1.1.2)}
-	\author{Jori Liesenborgs\\
-	        {\tt jori@lumumba.uhasselt.be} }
-	\date{September 14, 2005}
-	\maketitle
-
-	\section{Introduction}
-
-	A lot of projects on which I'm working use threads. To be able to
-	use the same code on both unix and MS-Windows platforms, I decided
-	to write some simple wrapper classes for the existing thread functions
-	on those platforms.
-
-	The JThread package is very simple: currently, it only contains two
-	classes, namely {\tt JThread} and {\tt JMutex}. As their names 
-	suggest, {\tt JThread} represents a thread and {\tt JMutex} a mutex.
-	The thread class only contains very basic functions, for example to
-	start or kill a thread.
-
-	\section{Copyright \& disclaimer}
-
-	Permission is hereby granted, free of charge, to any person obtaining a
-	copy of this software and associated documentation files (the "Software"),
-	to deal in the Software without restriction, including without limitation
-	the rights to use, copy, modify, merge, publish, distribute, sublicense,
-	and/or sell copies of the Software, and to permit persons to whom the
-	Software is furnished to do so, subject to the following conditions:
-
-	The above copyright notice and this permission notice shall be included
-	in all copies or substantial portions of the Software.
-
-	THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-	OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-	FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
-	THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-	LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-	FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
-	IN THE SOFTWARE.
-
-	\section{Usage}
-
-	Here follows a description of the {\tt JThread} and {\tt JMutex} classes. 
-	Note that functions with return type {\tt int} always return a value of zero
-	or more on success and a negative value in case something went wrong.
-
-	\subsection{{\tt JMutex}}
-
-	The class definition of {\tt JMutex} is shown below. Before you can use an
-	instance of this type, you must first call the {\tt Init} function. You can
-	check if the mutex was already initialized by checking the return value
-	of {\tt IsInitialized}. After the initialization, the mutex can be locked
-	and unlocked by calling the functions {\tt Lock} and {\tt Unlock} respectively.
-
-\begin{lstlisting}[frame=tb]{}
-class JMutex
-{
-public:
-	JMutex();
-	~JMutex();
-	int Init();
-	int Lock();
-	int Unlock();
-	bool IsInitialized();
-};	
-\end{lstlisting}
-
-	\subsection{{\tt JThread}}
-	
-	To create your own thread, you have to derive a class from {\tt JThread},
-	which is depicted below. In your derived class, you have to implement
-	a member function {\tt Thread}, which will be executed in the new thread.
-	Your own {\tt Thread} implementation should call {\tt ThreadStarted}
-	immediately.
-
-	To start your thread, you simply have to call the {\tt Start} function.
-	This function finishes when your own {\tt Thread} function has called
-	{\tt ThreadStarted}. This way, when the {\tt Start} function
-	finishes, you can be really sure that your own {\tt Thread} implementation
-	is really running.
-
-	You can check if the thread is still running by calling {\tt IsRunning}.
-	If the thread has finished, you can check its return value by calling
-	{\tt GetReturnValue}. Finally, in case your thread gets stuck, you can
-	end it by using the {\tt Kill} function.
-
-	You should be careful with this {\tt Kill} function: if you call it when
-	the thread is working with a mutex (for example an internal mutex), this
-	mutex can be left in a locked state, which in turn can cause another thread
-	to block. You should only use the {\tt Kill} function when you're absolutely
-	sure that the thread is stuck in some loop and cannot be ended otherwise.
-
-\begin{lstlisting}[frame=tb]{}
-class JThread
-{
-public:
-	JThread();
-	virtual ~JThread();
-	int Start();
-	int Kill();
-	virtual void *Thread() = 0;
-	bool IsRunning();
-	void *GetReturnValue();
-protected:
-	void ThreadStarted();
-};
-\end{lstlisting}
-	
-\end{document}
-

libs/jrtplib/examples/Makefile.am

-noinst_PROGRAMS = example1 example2 example3 example4
-
-example1_SOURCES = example1.cpp
-example2_SOURCES = example2.cpp
-example3_SOURCES = example3.cpp
-example4_SOURCES = example4.cpp
-
-INCLUDES = @RTP_JTHREADINCLUDES@ -I ../src/
-LDADD = ../src/.libs/libjrtp.a @RTP_LINKLIBS@
-