I think it might be procedure looks like used than link VC++ compiled
DLL with lcc (pedump + buildlib) but with another tools. Unfortunately
I did not find any information about.

"slava.pnp@gmail.com" <slava.pnp@gmail.com> writes:

> I think it might be procedure looks like used than link VC++ compiled
> DLL with lcc (pedump + buildlib) but with another tools. Unfortunately
> I did not find any information about.
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.

On Feb 12, 2:18 pm, "slava....@gmail.com" <slava....@gmail.com> wrote:
> I think it might be procedure looks like used than link VC++ compiled
> DLL with lcc (pedump + buildlib) but with another tools. Unfortunately
> I did not find any information about.

I found answer by myself. One should convert lcc .lib files to
msvc .lib using Microsoft LIB tool. For example "LIB /
OUT:some_lcc_dll_msvc.lib some_lcc_dll.lib", where some_lcc_dll.lib
is .lib file came with lcc DLL and produced some_lcc_dll_msvc.lib will
be used with MS LINK for implicit linking lcc DLL.

On 12 =C6=C5=D7, 17:35, Friedrich Dominicus <just-for-news-fr...@q-software-=

solutions.de> wrote:
> "slava....@gmail.com" <slava....@gmail.com> writes:
> > I think it might be procedure looks like used than link VC++ compiled
> > DLL with lcc (pedump + buildlib) but with another tools. Unfortunately
> > I did not find any information about.
>
> 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.

"slava.pnp@gmail.com" <slava.pnp@gmail.com> writes:


>
> 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. 

Regards
Friedrich

-- 
Please remove just-for-news- to reply via e-mail.