Undefined externals when linking DLL to Visual C?

FT_CreateDeviceInfoList() is not declaring any calling convention in the . H file, so it uses whatever the compiler's default calling convention is. Your compiler is defaulting to cdecl which is normal behavior for most C++ compilers.

Chances are that the compiler that created the DLL is actually using a different default calling convention instead. Try editing the . H file to specify stdcall for example, and see if it makes any difference, eg.

What you're doing should work as far as I can see. But you can always just forget about the . Lib file and use the DLL directly, loading it with LoadLibrary and getting the addresses of the functions you want to use with GetProcAddress.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.