Something does not fit the picture. You do not link a DLL statically
to a system. What you might want is building a static library and link
against it, that is easy done. Just build the static library with
lcc-win32 and then just add the static library to the link stage of
the MSVC project.
Regards
Friedrich
--
Please remove just-for-news- to reply via e-mail.
I mean implicitly link to a lcc compiled DLL. I don't have source
code, I only have a header, DLL and .lib file. But linking with MSVC++
using that .lib file is impossible.
>
> I mean implicitly link to a lcc compiled DLL. I don't have source
> code, I only have a header, DLL and .lib file. But linking with MSVC++
> using that .lib file is impossible.
I see that is something completly different. The DLL was compiled with
lcc-win32 and you know like to use it, but you do not have access to
the sources. Then you have to use LoadLibrary and GetProcAddress to
fetch out the functions you like to call. You just have to see that
you use the proper name from the DLLs you can check the names with the
pedump utilitiy.