readme.txt

h.248协议源码

Supported Target OS's
---------------------
Solaris 8
Solaris 7
Solaris 2.6

IMPORTANT: The Recommended Solaris Patch Cluster for Solaris 7 & 8 is required (Aug 8, 2001
or newer).  There are several patches in these clusters required to correct problems in the 
the Solaris recursive mutex.  

Supported Host OS's
-------------------
Solaris 8
Solaris 7
Solaris 2.6

Supported compiler's
--------------------
GNU C 2.95 or newer
Sun Workshop C Compiler 5.0
Sun Workshop C Compiler 4.2


Build Environment
------------------
The build environment on Solaris depends on which compiler is going
to be used for building the toolkit. For all cases, it requires installing
and configuring the compiler as per the compiler installation instructions.
This includes and default library paths, license file information, and
execution paths so that the compilers are accessible from the command line.

Also, regardless of the compiler, building the toolkit requires GNU Make
version 3.78 or newer. A recent version can can be easily downloaded from
http://www.gnu.org and built using the installed compiler. The make executable
should be renamed gmake and put into a directory that is included in the path.


Build Configuration
-------------------
For Solaris, the TARGET_OS and HOST_OS should be set to solaris. The
TARGET_FAMILY, TARGET_CPU, and COMPILER_CPU should be set to sparc,
however, these three parameters are assumed (and actually ignored).
Set the COMPILER parameter to the compiler that is to be used.
For simplicity here are two examples of build parameters settings
as they should appear (and can simply be copied there) in the
default.mak file; one for the Sun Workshop compiler and one for the
GNU compiler.

# Build Parameters - Sun Workshop
TYPE ?= debug
TARGET_OS ?= solaris
HOST_OS ?= solaris
TARGET_FAMILY ?= sparc
TARGET_CPU ?= sparc
COMPILER_CPU ?= sparc
COMPILER ?= sparcworks

# Build Parameters - GNU on Solaris
TYPE ?= debug
TARGET_OS ?= solaris
HOST_OS ?= solaris
TARGET_FAMILY ?= sparc
TARGET_CPU ?= sparc
COMPILER_CPU ?= sparc
COMPILER ?= gnu


Building the Toolkit
-------------------------
Follow the standard command line build instructions as described in
this readme file.

4. Red Hat Linux Target Environment
=============================

Supported Target OS's
---------------------
Red Hat 6.2 (Linux 2.2)**
Red Hat 7.1 (Linux 2.4)**

** Requires Pentium or higher CPU (or compatible)


Supported Host OS's
-------------------
Red Hat 6.2 (Linux 2.2)
Red Hat 7.1 (Linux 2.4)

Supported compiler's
--------------------
GNU C 2.91 or newer (for Red Hat 6.2)
GNU C 2.96 or newer (for Red Hat 7.1)


Build Environment
------------------
For Red Hat Linux insure that the compiler development tools (gnu) were installed.


Build Configuration
-------------------
For Red Hat Linux, the TARGET_OS and HOST_OS should be set to redhat. The
TARGET_FAMILY, TARGET_CPU, and COMPILER_CPU should be set to i386,
however, these three parameters are assumed (and actually ignored).
Set the COMPILER parameter to gnu.

For simplicity here are two examples of build parameter settings
as they should appear (and can simply be copied there) in the
default.mak file.

# Build Parameters - GNU on Red Hat
TYPE ?= debug
TARGET_OS ?= redhat
HOST_OS ?= redhat
TARGET_FAMILY ?= i386
TARGET_CPU ?= i386
COMPILER_CPU ?= i386
COMPILER ?= gnu


Building the Toolkit
-------------------------
Follow the standard command line build instructions as described in
this readme file.

5. Tru64 Target Environment
=============================

Supported Target OS's
---------------------
Tru64 5.0

Supported Host OS's
-------------------
Tru64 5.0
IMPORTANT: In order to access a linear time source (one that does not jump backward or 
forward due to clock adjustments), the sysdev0 driver must be installed.  To install 
this driver, as root, do the following:
	cd /dev
	./MAKEDEV sysdev0
Failing to do install driver will cause an assertion to fail upon Toolkit initialization.

Supported compiler's
--------------------
cc 5.0

Build Environment
------------------
Building the toolkit requires GNU Makeversion 3.78 or newer. A recent version 
can can be easily downloaded from http://www.gnu.org and built using the installed 
compiler. The make executable should be renamed gmake and put into a directory that 
is included in the path.


Build Configuration
-------------------
For Tru64, the TARGET_OS and HOST_OS should be set to tru64. The
TARGET_FAMILY, TARGET_CPU, and COMPILER_CPU should be set to alpha,
however, these three parameters are assumed (and actually ignored).
Set the COMPILER parameter to decc.

For simplicity here is an example of build parameter settings
as they should appear (and can simply be copied there) in the
default.mak file.

# Build Parameters - GNU on Red Hat
TYPE ?= debug
TARGET_OS ?= tru64
HOST_OS ?= tru64
TARGET_FAMILY ?= alpha
TARGET_CPU ?= alpha
COMPILER_CPU ?= alpha
COMPILER ?= decc


Building the Toolkit
-------------------------
Follow the standard command line build instructions as described in
this readme file.

6. VxWorks Target Environment
=============================

Supported Target OS's
---------------------
VxWorks 5.4 or higher


Supported Host OS's
-------------------
Solaris 7
Windows NT 4.0
Windows 2000

Supported compiler's
--------------------
GNU C (VxWorks variant included as part of Tornado 2)


Build Environment
------------------
The first thing that must be done to set up the environment is
to install Tornado 2 which includes all of the VxWorks compilers,
tools, libraries, etc., which are needed. Once this is done,
the following environment variables need to be set:
WIND_BASE=C:/TORNADO
SET WIND_HOST_TYPE=x86-win32
GCC_EXEC_PREFIX=c:/TORNADO/host/x86-win32/lib/gcc-lib/

On Windows, also set the following environment variable so that
the compiler knows what directory to use for scratch space:
TMPDIR=D:/TEMP

Obviously, the values of for these settings are dependent upon
where Tornado was installed and what the host OS is. The above
settings are for a Windows host with Tornado installed in
C:\TORNADO. Note that for both Unix and Windows, a forward
slash ("/") is used for paths.

The GCC_EXEC_PREFIX points the compiler to where the target
specific components for the compiler are installed. For
more information on this setting see the GNU Compiler
documentation.

IMPORTANT: The GNU compiler requires the trailing "/" at the
end of the GCC_EXEC_PREFIX path.

Unfortunately, the GNU utilities included with Tornado are so
old that they can not be used with the makefiles included with
this toolkit. The solution to this depends on the host OS
being used.

On Solaris the solution is relatively simple. Download a recent version
of GNU Make (version 3.78 or newer) from http://www.gnu.org. It must be built
with a native Solaris compiler, so if one doesn't exist on the Sun being used,
also download and install the GNU compiler for Sparc. The make executable
should be renamed gmake and put into a directory that is included in the path.
Then, add the Tornado executables directory into the path, but at the
end so that the native Solaris and GNU tools are used for common commands
(like gmake, sed, sort, etc). That directory should look something like
this: "%WIND_BASE%/host/solaris/bin". Once this is done, the build environment
for Solaris is ready.

On Windows, there are two choices. The first is to download native versions of
all of the individual tools required (see list given in the Build Requirements
section of this readme file). Unfortunatly finding recent version of
Windows GNU tools is not easy. Once they are acquired place them in a directory
and put that directory in the path along with, but in front of, the Tornado
executables directory. Thus if those tools are places in a C:\TOOLS directory,
set the path like so:
SET Path=C:\TOOLS;C:\TORNADO\host\x86-win32\bin;%PATH%

The second, and probably preferable option for Windows, is to download the
Cygwin GNU package from http://www.cygwin.com. Instructions for setting up and
installing this package can be found on the Cywin web site but here is a set
of "quick-start" instructions:
     1. Go to http://www.cygwin.com
     2. Go to the download page.
     3. Select an FTP mirror site near you.
     4. Download the SETUP.EXE program
     5. run the SETUP.EXE program
     6. Tell Setup that you want to install from the Internet
     7. Select the FTP site you downloaded SETUP.EXE from
     8. By default it will install all Cygwin packages. Unless disk space
        is limited or you have a slow internet connection, just install
        all of them.
     9. Make sure to tell setup to install into the C:\cygwin directory (you
        can use any drive letter). Note: make sure it doesn't try to install
        into C:\, or things could get messy.
     10. Tell Setup to use DOS text by default
     11. Wait for all packages to install and exit Setup. You can put
         the icons on the desktop and the Start Menu if you like. It's
         a good idea to have it install the icons on one or the other so you 
         see how to start a bourne command shell, even though building this 
         toolkit will not be done from that shell (although make will use the 
         shell itself).
     12. Place the cygwin bin directory (ie C:\cygwin\bin) at the front of
         the Windows path. Putting it at the front is important so
         that the proper commands (like sort, for example) are called.
	 This can be done only when building this toolkit or on a system
         wide basis since the Cygwin tools can be very useful for a number
         of things.
Finally, place the Tornado execuables directory in the path AFTER the Cygwin
directory. Thus set it like so:
SET Path=%PATH%;%WIND_BASE%\host\x86-win32\bin

Once that is done the build environment is ready.


Build Configuration
-------------------
For VxWorks, the TARGET_OS should be set to vxworks and the COMPILER
should be set to gnu. Set HOST_OS to solaris or win32 as approriate.
The TARGET_FAMILY, TARGET_CPU, and COMPILER_CPU need to be set specifically
based on the target precessor:
     TARGET_FAMILY	This is used to find the proper compiler tools
			in the Tornado environment. One example is
			that for the Power PC, the compiler is called
			ccppc, thus TARGET_FAMILY needs to be set to
			ppc.

     TARGET_CPU		This is used to find the proper libraries for
			the target CPU and is defined during compilation
			for use by VxWorks include files. One example is
			that for an embedded Power PC 603 based CPU
			(like the 860 or 8260), the closest compatible