As for the Win32::API method, I think it finds both the dll and the function in it. If it failed at either task, it would croak something like "Undefined sub &main::RegisterClient2 in..." - which it did, when I misspelled the path. I'll try to check $^E tomorrow, but the fact that the whole program crashed when I used the $function = Win32::API->new(), $function->Call() syntax doesn't fill me with too much hope.
in reply to Re: Calling a function form an external DLL with Inline::C on windows
in thread Calling a function form an external DLL with Inline::C on windows
As for the Inline method: no, no .lib, only the .dll.
I've found some advice on the net that said MinGW is able to use the dll directly. However, there might be a path problem related to MinGW's setup (or whatever) here that I can't figure out.
I don't have dumpbin.exe, at least I'm not aware of it.
(Can't tell now, as I'm writing from a different machine)