readme.txt

h.248协议源码

			definition defined by VxWorks is PPCEC603 and
			thus that is what TARGET_CPU should be set to.

     COMPILER_CPU	This is used to tell the compiler what CPU to
			compile for. This is based on the allowed
			settings for the GNU compiler and is described
			in the GNU and VxWorks documentation. One
			example is that for an embedded Power PC 603e
			based CPU (like the 860 or 8260), the closest
			compatible CPU option is 603e, and thus that is
			what COMPILER_CPU should be set to. Also note
			that the compiler may require additional switches
			for a paraticular CPU which must be defined on the
			CFLAGS line of the default.mak file.

Here is an example of the Build Parameters and CFLAGS settings for a Power PC
8260 being built in debug mode on a Windows host for a VxWorks target. In this
example, the -msoft-float is required because the compiler doesn't know 8260
and is treating it like a 603e but the 8260 doesn't have floating point hardware.
The -fno-for-scope is required by VxWorks as indicated in their PowerPC specific
documentation. This example could be copied directly into the default.mak for
this particular environment:

# Build Parameters
TYPE ?= debug
TARGET_OS ?= vxworks
HOST_OS ?= win32
TARGET_FAMILY ?= ppc
TARGET_CPU ?= PPCEC603
COMPILER_CPU ?= 603e
COMPILER ?= gnu

# Additional special compiler flags
CFLAGS := -msoft-float -fno-for-scope


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


Linking with the Toolkit Libraries
---------------------------------------
Important Note:  Megaco require libgcc.a to be linked in when
building an application. Make sure to link your application with the approriate
libgcc.a library for the environment it is being used in. For example,
if Tornado is installed in C:\Tornado2ppc on a windows host, the
target is a powerpc with no hardware floating point support, and the
version of gcc is cygnus-2.7.2-960126, then the proper libgcc.a to link
with would be:
C:/Tornado2ppc/host/x86-win32/lib/gcc-lib/powerpc-wrs-vxworks/cygnus-2.7.2-960126/soft-float/libgcc.a
Check the VxWorks and Tornado documentaion for more information about this
library.

In order to start the megacomg application, simply call the following function:
void appMain();

There are currently no parameters to appMain().
For Megaco, the configuration parameters are set in the 
/megaco/client/megacomg/megacomg.c file via a number of initialization strings. 
Once called the application will start and this function never returns.

In order to start the megacomgc application, simply call the following function:
void appMain(void) 

The mgc address is taken from RV_MGC_IP, and the terminations information 
is taken from the configtable structure.

Other Notes
-----------
IMPORTANT: Make sure that the VxWorks configuration macro BSD43_COMPATIBLE
           is NOT defined when building your VxWorks image. The default
           configAll.h file has it defined but when creating a project with
           Tornado it (by default) undefines it. So VxWorks applications
           built with Tornado will normally work fine but building outside
           of Tornado requires adding a #undef BSD43_COMPATIBLE to your
           configuration header file.


7. PSOS Target Environment
==========================

Supported Target OS's
---------------------
pSOS 2.50 or higher


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


Supported compiler's
--------------------
Diab (included in pRISM+ development environment)


Build Environment
------------------
The first thing that must be done to set up the environment is
to install pRISM+ which included all of the Diab compilers,
tools, libraries, etc., which are needed. The remaining
setup depends on which host environment that is being used.

On Solaris, simply set the following environment variables:
PSS_ROOT	- pRISM root directory for target (ie /usr/isippc/pssppc.250)
PSS_BSP		- directory of BSP to be used (ie /usr/isippc/pssppc.250/bsps/est8260)
DIABLIB		- directory of Diab compiler (ie /usr/isippc/diab/4.2b)

Also, if the license file is not already set up then set the following:
LM_LICENSE_FILE	- license file location (ie /usr/licenses/license.dat)

Finally, make sure that the diab compiler (ie /usr/isippc/diab/4.2b/solaris/bin)
is in the path. This completes the build environment for Solaris. More information
about these environment settings can be found in the pRISM documentation.

For Windows, there are 2 choices. First is to use the MKS Toolkit
included with the pRISM+ tools and add GNU Make. To do this, a the
build must be run from a shell set up by the environment script. This
script is located in the pRISM+ directory and is called env"target".ksh
where "target" is the processor family for the target. For example, if pRISM
for the Power PC (PPC) is installed in C:\ISIPPC, it would be c:\ISIPPC\envppc.ksh.
The "DOS Prompt PPC" that pRISM+ puts in the start menu runs a creates a shell
with that script, so you could run that and then simply add the GNU make path
to the beginning of the path. A GNU Make is included with pRISM+ (in
%PSS_ROOT%/bin/win32/gnu) but it is slightly older than 3.78. You must download
a native windows version of GNU make and either update the one the in the
pRISM+ directory or put it in a seperate directory. In either case, add
the directory to the FRONT of the path so make uses that version instead of the
MKS Toolkit version.

The second 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
        islimited 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. Its
         a good idea to have it do one 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 usefull for a number
         or things.

Once the Cywin tools are installed, put the Diab compiler directory
into the that (order doesn't matter). If pRISM+ was installed in
C:\ISIPPC, then the Diab directy to put in the path would be
C:\ISIPPC\diab\4.2b\win32\bin

Once this is done, then the required environment variables need to be set:
PSS_ROOT	- pRISM root directory for target
PSS_BSP		- directory of BSP to be used
DIABLIB		- directory of Diab compiler
LM_LICENSE_FILE	- license file location

IMPORTANT: For PSS_ROOT, PSS_BSP, and DIABLIB, use a forward slash ("/")
           for directory paths, do NOT use a back-slash ("\"). For
	   LM_LICENSE_FILE, use the standard back-slash ("\").

An example environment set-up for a EST Power PC 8260 board would be:
SET PSS_ROOT=C:/ISIPPC/pssppc.250
SET PSS_BSP=C:/ISIPPC/pssppc.250/bsps/est8260
SET DIABLIB=C:/ISIPPC/diab/4.2b
SET LM_LICENSE_FILE=C:\ISIPPC\licenses\license.dat
SET Path=C:\ISIPPC\diab\4.2b\win32\bin;%PATH%


Build Configuration
-------------------
For pSOS, the TARGET_OS should be set to psos and the COMPILER
should be set to diab. Set HOST_OS to solaris or win32 as approriate.
The COMPILER_CPU needs to be set based on the target CPU as per
the Diab compiler -t option. Thus, for the a Embedded Power PC 603
CPU, it would be set to PPC603ES (E = elf format and S = software
floating point). Set TARGET_FAMILY and TARGET_CPU to be the same
as COMPILER_CPU since they are not used by the Diab compiler
(and are actually ignored).

Here is a default.mak build parameters example for a Power PC 8260
target running pSOS being built for release on a Windows host:

# Build Parameters
TYPE ?= release
TARGET_OS ?= psos
HOST_OS ?= win32
TARGET_FAMILY ?=  PPC603ES
TARGET_CPU ?= PPC603ES
COMPILER_CPU ?= PPC603ES
COMPILER ?= diab


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


Linking with the Toolkit Libraries
---------------------------------------
There are two board specific pieces of information that the Toolkit
requires for operation that must be provided by the implementation.
They are the the number of clock ticks per second and the hostname. These
values are in the pSOS and pNA configuration tables, respectivly.
Expects the pSOS configuration table to be in a global stucture
called PsosCfg (declared as type pSOS_CT) and the pNA configuration
table to be in a global structure called PnaCfg (declared as type pNA_CT).
If the application is built with the pRISM tools, these global structures
are make available in every application and will automatically be used.
If an application is being built without the pRISM tools (and specifically
the pRISM startup code), then these structures will need to be made available
by the application.

Note that there are no working versions of the megacomg and megacomgc apps
for pSOS yet.

In order to start the megacomg application, simply call the following function:
void appMain(int argc, char **argv, char **env, void *exit_param, const char *console_dev);

The parameters to appMain are currently ignored. Configuration
parameters must be set in the megaco/client/megacomg/rvmegacomg.c file itself via a
number of #define parameters. Once called the application will start and
this function never returns. The function parameters are set up so that
this application can be called from pShell. It is then very easy to call
megacomg from the netutils demo application by simply puting the following
into the pShell configuration array in root.c of that demo application:
	{ "megacomg", "MEGACOMG Application",appMain, "megacomg", 100, 8196, -1, 0, 0 }

You will also need to declare the appMain function like so:
	extern void appMain(void);

Then manually modify the makefile of the netutil demo application to
put the Toolkit lib directory into the library path and to link
with all of the libraries that get built by the Toolkit. When the
modified demo application is build, you can simple type megacomg at
the pShell command line to start the megacomg application.

For the megacomgc application, there is currently no easy way to run it with
the netutil demo application. A stand-alone application will have to be
built. From that application, to start the megacomgc application, simply call
the following function:

void appMain(void) 

The mgc address is taken from RV_MGC_IP, and the terminations information 
is taken from the configtable structure.


8. OSE Target Environment
==========================

Supported Target OS's
---------------------
OSE 4.2 or higher**

**requires Level C Kernel, along with the Pthreads, RTC, Heap Manager, and
	DNS client modules.


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


Supported compiler's
--------------------
Greenhills Multi 2000 3.0**

**Note: The Greenhills compiler must be set for compatability
mode. The "Next Generation" compiler can not yet be used due
to some unresolved problems with that compiler.


Build Environment
------------------
The first thing that must be done to set up the environment is
to install both Multi 2000 and OSE. Make sure to follow the
OSE specific instructions provided by Greenhills in the Multi 2000
documentation. Also make sure that the license manager is setup up
properly for OSE as described in the OSE documentation. The remaining
setup depends on which host environment that is being used.

On Solaris, simply set the following environment variable:
OSE_ROOT	- OSE root directory