On Sep 19, 2006, at 7:28 AM, Brian Vandenberg wrote:
I'm writing a plugin (win32 dev environment) in which I need
access to
functionality in base64.x and crypt-md5.x.
".x"? There aren't any ".x" files in Wireshark; did you mean ".c"?
I had been under the
[faulty?] assumption that the object files for these two are compiled
into libwireshark.lib,
That's a correct assumption.
The incorrect assumption you're making is that compiling them in is
sufficient to make them available for your plugin; while that's true
of Un*x dynamic shared library mechanisms (anything external is
exported), it's apparently not true of the Windows mechanism -
routines have to be in the .def file used when the library is built.
I've checked in a change to add the routines in epan/base64.c and epan/
crypt-md5.c to the libwireshark .def file. Unfortunately, that
doesn't help you unless you build Wireshark, in its entirety, from the
latest top-of-tree source from the Wireshark repository, or grab the
next buildbot build (build 728) or a later build.
