On Fri, May 23, 2008 at 9:32 PM, Thomas Hruska <[EMAIL PROTECTED]> wrote: > Brett McCoy wrote: >> I found a tool called PEBrowse which can be used to inspect symbols in >> a DLL or EXE, and sure enough, so symbols were being exported. I >> abandoned the use of the .def file and just added the export symbols >> into the linker options. And whaddya know? It worked. Plugin happily >> loaded into the host application and is functional, and now I can >> debug away. > > Meh. I tried PEBrowse a while back. It doesn't work very well. And is > WAY overkill for your needs (i.e. To determine what exports, if any, are > in the DLL). Dependency Walker is really all you need.
OK, I will try DependencyWalker, too. For what I was doing, PEBrowse did what I needed, to show whether or not my DLL was exporting symbols. > If you are going to have a lot of exports, a DEF file is a much cleaner > way to go. But as long as it works... Just 5 or 6 functions need to be exported. After doing some research, it seems the SDK designer could also have declared the Plugin functions in the supplied header with __declspec(dllexport), so the functions could be exported that way (there is a defined group of functions that MUST be exported for the plugins to work). -- Brett ------------------------------------------------------------ "In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world." -- Jelaleddin Rumi
