osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity
wireshark/plugins
History
Guy Harris 1f4073974f Check for bogus attribute lengths. 
svn path=/trunk/; revision=12505
 		2004-11-10 10:46:40 +00:00
..
acn From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
artnet From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
asn1 From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
ciscosm From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
docsis From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
enttec From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
giop From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
gryphon From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
irda From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
lwres From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
megaco From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
mgcp From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
opsi Check for bogus attribute lengths. 2004-11-10 10:46:40 +00:00
pcli From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
rdm From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
rlm From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
rtnet From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
rudp From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
v5ua From Lars Roland: we need to define _NEED_VAR_IMPORT_ in plugins if we 2004-10-01 19:50:03 +00:00
Makefile.am From Laurent Rabret: OPSI support. 2004-07-21 06:31:33 +00:00
Makefile.nmake From Laurent Rabret: OPSI support. 2004-07-21 06:31:33 +00:00
README.interface From Matthijs Melchior: generate all declarations and definitions for 2003-07-18 03:02:12 +00:00
Xass-list Add proto_tree_add_debug_text(), rtcp_add_address(), and 2004-09-23 07:32:58 +00:00
Xplugin_api.c Add proto_tree_add_debug_text(), rtcp_add_address(), and 2004-09-23 07:32:58 +00:00
Xplugin_api.h Add proto_tree_add_debug_text(), rtcp_add_address(), and 2004-09-23 07:32:58 +00:00
Xplugin_api_decls.h Add proto_tree_add_debug_text(), rtcp_add_address(), and 2004-09-23 07:32:58 +00:00
Xplugin_table.h Constify more pointer arguments. 2004-10-11 18:35:26 +00:00
plugin_api.c Set the svn:eol-style property on all text files to "native", so that 2004-07-18 00:24:25 +00:00
plugin_api.h In "plugins/plugin_api.h", don't include stuff required for the plugin 2004-09-29 22:20:21 +00:00
plugin_api_decls.h Set the svn:eol-style property on all text files to "native", so that 2004-07-18 00:24:25 +00:00
plugin_api_defs.h Set the svn:eol-style property on all text files to "native", so that 2004-07-18 00:24:25 +00:00
plugin_api_list.c Constify more pointer arguments. 2004-10-11 18:34:54 +00:00
plugin_gen.py Set the svn:eol-style property on all text files to "native", so that 2004-07-18 00:24:25 +00:00
plugin_table.h Set the svn:eol-style property on all text files to "native", so that 2004-07-18 00:24:25 +00:00

README.interface 

README.interface

When developing a plugin in the Win32 world, it is nessecary
to explicitly export addresses from the main process to the
plugin.  ethereal does have a mechanism for this, and it uses
the file 'plugin_api_list.c' to list declarations for everything
that needs to be exported.

The build process of ethereal needs this list in 5 different forms.

These are generated by a Python script and saved in the X* files
in this directory.

I do not have a real C parser in Python to read the input file...,
so I have used 'gcc -aux-info xyzzy ...' to clean up any formatting
preferences in the input file and create the file named 'xyzzy'
that contains a neatly formatted list of declarations.  This list
can be parsed with a regular expression to extract the required
info.

Use the following procedure when updateing the plugin_api_list.c file:

nmake -f Makefile.nmake xyzzy
nmake -f Makefile.nmake

The 'xyzzy' makefile target is the only target that depends on gcc.
This can be done on a Unix machine or you can use cygwin gcc.