wm_PNE_3_3
所属分类:VxWorks
开发工具:Unix_Linux
文件大小:4018KB
下载次数:33
上传日期:2009-03-27 18:00:44
上 传 者:
AfE
说明: wm PNE 3.3 source code, running at more than vxworks6.x version.
文件列表:
wm_PNE_3_3 (0, 2009-03-30)
wm_PNE_3_3\h (0, 2009-03-30)
wm_PNE_3_3\h\wm (0, 2009-03-30)
wm_PNE_3_3\h\wm\common (0, 2009-03-30)
wm_PNE_3_3\h\wm\common\backstop (0, 2009-03-30)
wm_PNE_3_3\h\wm\common\backstop\common.h (1565, 2009-03-16)
wm_PNE_3_3\h\wm\common\backstop\oemtypes.h (1677, 2009-03-16)
wm_PNE_3_3\h\wm\common\bug.h (8930, 2009-03-16)
wm_PNE_3_3\h\wm\common\bugdef.h (18482, 2009-03-16)
wm_PNE_3_3\h\wm\common\cmn_init.h (3356, 2009-03-16)
wm_PNE_3_3\h\wm\common\config.h (2070, 2009-03-16)
wm_PNE_3_3\h\wm\common\des.h (2549, 2009-03-16)
wm_PNE_3_3\h\wm\common\dyncfg.h (11895, 2009-03-16)
wm_PNE_3_3\h\wm\common\fixed64.h (2154, 2009-03-16)
wm_PNE_3_3\h\wm\common\fldmacro.h (2921, 2009-03-16)
wm_PNE_3_3\h\wm\common\glue.h (4623, 2009-03-16)
wm_PNE_3_3\h\wm\common\hmac.h (3082, 2009-03-16)
wm_PNE_3_3\h\wm\common\md4.h (2891, 2009-03-16)
wm_PNE_3_3\h\wm\common\md5.h (4846, 2009-03-16)
wm_PNE_3_3\h\wm\common\prng.h (2052, 2009-03-16)
wm_PNE_3_3\h\wm\common\sha.h (2594, 2009-03-16)
wm_PNE_3_3\h\wm\common\snprintf.h (1918, 2009-03-16)
wm_PNE_3_3\h\wm\common\stdf.h (2533, 2009-03-16)
wm_PNE_3_3\h\wm\common\thread.h (7454, 2009-03-16)
wm_PNE_3_3\h\wm\common\types.h (5114, 2009-03-16)
wm_PNE_3_3\h\wm\common\weakprng.h (2108, 2009-03-16)
wm_PNE_3_3\h\wm\demo (0, 2009-03-30)
wm_PNE_3_3\h\wm\demo\bpf.h (2326, 2009-03-16)
wm_PNE_3_3\h\wm\demo\bpfdrive.h (2313, 2009-03-16)
wm_PNE_3_3\h\wm\demo\bsdif.h (2179, 2009-03-16)
wm_PNE_3_3\h\wm\demo\bug_conf.h (3984, 2009-03-16)
wm_PNE_3_3\h\wm\demo\dlpi.h (1717, 2009-03-16)
wm_PNE_3_3\h\wm\demo\dlpidrv.h (1638, 2009-03-16)
wm_PNE_3_3\h\wm\demo\dsmemcfg.h (5046, 2009-03-16)
wm_PNE_3_3\h\wm\demo\firewall.h (2152, 2009-03-16)
wm_PNE_3_3\h\wm\demo\if_ether.h (1473, 2009-03-16)
wm_PNE_3_3\h\wm\demo\keyboard.h (2125, 2009-03-16)
wm_PNE_3_3\h\wm\demo\keyword.h (2206, 2009-03-16)
wm_PNE_3_3\h\wm\demo\main.h (2427, 2009-03-16)
wm_PNE_3_3\h\wm\demo\netconf.h (3154, 2009-03-16)
... ...
As of this release of WindManage SNMP (9.3), the layout of the SNMP code base
has changed significantly. A full description of the previous and current file
layout schemes can be found in the WindManage SNMP 9.3 Release Notes.
Customers who have written applications based on WindManage SNMP 9.2 and older
will need to make changes to the customer-added sections of their applications
in order to upgrade to version 9.3.
These changes will be, in general, of two forms:
a) moving files from one location to the new, analogous location in the
the source tree layout.
b) editing customer-added files to reflect the new locations of #include
files needed to use WindManage SNMP. For example, the file formerly
known as is now .
How time-consuming a task making these changes will be depends entirely on
the scope of the customer application and how many external files the customer
has added.
In order to make task (b) a little easier on the application developer, we
have included a small tool which will make most, if not all, of the include
file path changes needed to migrate application code from version 9.2 and
previous to version 9.3. This tool is provided in the form of a Bourne Shell
script, and will run on any Un*x system which has a standard Bourne shell and
the 'sed' utility. It will also run under the Cygwin version of these utilities
which have been provided with WindManage SNMP, on a Windows NT/2000/etc
machine.
The tool is called "chgipath.sh", and will be found in the
"target/src/wrn/wm/tools/include_path_tool" directory.
What this tool is:
This tool is provided to help with the tedious task of changing include
paths for the WindManage SNMP include files in customer-added application
code built using WindManage SNMP.
What this tool is not:
This tool is not meant to be run on any files that are part of an original
WindManage SNMP distribution. In particular, this tool will *not* convert
a WindManage SNMP 9.2 release into a WindManage SNMP 9.3 distribution.
Also, if your application made modifications to the VxWorks SNMP agent
source files, you will need to port these changes into the current VxWorks
agent source files. This tool can not and does not do that job.
You may wish to use this tool if:
You have application source files which were previously compiled with
WindManage SNMP 9.2 or earlier, and wish to migrate to WindManage SNMP 9.3.
If you were just using the supplied MIB2 implementation which came with
WindManage SNMP 9.2, and did not implement any of your own MIBS, You do
not need to use this tool at all.
Using chgipath.sh:
First, BACK UP YOUR SOURCE TREE before using this tool. Lack of disk space,
strange directory permissions, etc are all ways the script could fail and
leave your tree in an unknown state. BACK UP YOUR SOURCE TREE.
Now that you have backed up your source tree, make a copy of the chgipath.sh
script in the directory where the files you want changed are located. If you
are running on a Windows machine, make sure you have already installed
WindManage SNMP version 9.3 into your Tornado installation, and have run the
torVars.bat script to set up your Tornado environment variables. The following
examples are written assuming you are running on a un*x machine, but will work
just as well in a Windows Command window.
"chgipath" takes as command arguments the filenames you wish to edit. By
default, chgipath only edits ".c" and ".h" files, ignoring any other file
types. See the "Changing default file types" for how to change this behavior.
OPTIONS:
-r if this option is given, chgipath will recursively process any
directories given on the command line (or found while processing
a directory given, etc). Without "-r", directories are ignored.
-s if "-s" is given, the current version of "file" is saved as
"file.old". Do not rely on this instead of backing up your source
tree!
General Usage:
$ sh chgipath.sh [-r] [-s] [...]
Examples:
$ sh chgipath.sh foo.c
edits "foo.c", and changes WindManage include file paths.
$ sh chgipath.sh -s foo.c
edits "foo.c", and changes WindManage include file paths. Leaves
the original version of "foo.c" in "foo.c.old"
$ sh chgipath.sh -s foo.c
edits "foo.c", and changes WindManage include file paths. Leaves
the original version of "foo.c" in "foo.c.old"
$ sh chgipath.sh -s -r foo.c foo.h file_directory
edits "foo.c" and "foo.h", and changes WindManage include file paths.
Goes into "file_directory" and processes all files there as well.
Leaves the original version of all files edited in ".old"
Changing default file types
By default, chgipath.sh only acts on ".c" and ".h" files. The types
of files it will process can be changed by setting the SUFFIXES
environment variable to be a list of the file types you wish to
process. (setting the environment variables is one place where
the procedure will vary for Windows and Unix boxes)
I.E:
(unix, bourne shell variants)
$ SUFFIXES=".cpp .c .h" sh chgipath.sh -s -r foo.c foo.h file_directory
will process .c, .h, and .cpp files.
(unix, C shell variants)
% setenv SUFFIXES=".cpp .c .h"
% sh chgipath.sh -s -r foo.c foo.h file_directory
(windows)
C:> set SUFFIXES=".c .cpp .h"
C:> sh chgipath.sh -s -r foo.c foo.h file_directory
近期下载者:
相关文件:
收藏者: