Re: Linking DLL Statically
- From: Max Bolingbroke <mb566@xxxxxxxxx>
- Date: Tue, 13 Jun 2006 13:11:34 +0100
anton bassov wrote:
Hi mate
//////
The process take place when we are linking with the lib file. I just wanted to this using a dll file instead of lib file.
//////
You cannot link with DLL file - this is what .lib files are for. If you don't want to use library file, the easiest thing to do is get the function's address by GetProcAddress(), and call the function by its address,
rather than name.
BTW, why do you ask all that??? What's wrong with .lib files????
Hi Anton
I believe what the OP is asking is for a way to include the actual object code of the DLL into his EXE so that he dosen't have to e.g. distribute the DLL file itself. The program I linked in my other reply to this thread does just that.
Max
.
- Follow-Ups:
- Re: Linking DLL Statically
- From: Aniruddha
- Re: Linking DLL Statically
- From: anton bassov
- Re: Linking DLL Statically
- References:
- Re: Re:Linking DLL Statically
- From: Aniruddha
- Re: Re:Linking DLL Statically
- From: anton bassov
- Re: Re:Linking DLL Statically
- Prev by Date: Re: without message queue
- Next by Date: Problem passing telnet socket to spawned process
- Previous by thread: Re: Re:Linking DLL Statically
- Next by thread: Re: Linking DLL Statically
- Index(es):
Relevant Pages
|