Ethereal-dev: Re: [Ethereal-dev] Can't compile Ethereal from current CVS on Windows.

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Mon, 25 Aug 2003 14:02:56 -0700

On Monday, August 25, 2003, at 1:41 PM, Gisle Vanem wrote:


Yes, if (t)ethereal.exe misses an export the plugin need, LoadLibrary
on the plugin.dll would simply fail w/o saying what symbols was missing
And if it doesn't miss any exports, presumably "LoadLibrary()" will succeed and bind references to the exported function from the module to the function in the main program, right? 


That's a drawback compared to the manual GetProcAddress() loading.
I assume that's what Glib uses.


What GLib's gmodule code uses, on Win32, is:

	LoadLibrary() to load a run-time-loadable module;

	GetProcAddress() to get a pointer to a function in a loaded module.


Agreed. And maybe we should make a Perl/Python script to add a .def
file entry for all prototypes beginning with ETR_API.
That might be useful, although not everybody building Ethereal necessarily has Perl or Python, so we should probably include the .def file in the distribution. (It would presumably be built by scanning .h files, so it should be made dependent on them, if possible - can nmake specify that something depends on, for example, "*.h" and "epan/*.h"?)