From: Mark Hahn <mchahn@...>
Date: 2001-12-24T12:58:36+09:00
Subject: [ruby-talk:29393] Re: x.dll versus x.lib in mswin32 ruby


> Is there a way to create a .lib from a .dll

I doubt anyone cares, but I found the answer to my own question:

1. Create a .DEF (module definition) file based on the DLL that you're
interested in.  I recommend using a free tool called MAKEDEF which you can
download here: http://codeguru.earthweb.com/tools/Makedef.shtmlTo create the
.DEF file, you would use the command as:

	MAKEDEF /DEF:x.DEF /IMAGE:x.DLL

2. Now that you have the .DEF file, use the LIB utility in Visual C++ 5 to
create a new import library based on that file. The command would be:

	LIB /MACHINE:IX86 /DEF:x.DEF /OUT:x.LIB

You now have a new import library that should be compatible with your
version of the compiler. By the way, you can use this method to create an
import library for any DLL.

-----Original Message-----
From: Mark Hahn [mailto:mchahn@facelink.com]
Sent: Sunday, December 23, 2001 3:36 PM
To: ruby-talk@ruby-lang.org
Subject: RE: [ruby-talk:29382] Re: x.dll versus x.lib in mswin32 ruby



Thanks.  (You can tell I'm not a windows programmer).

Is there a way to create a .lib from a .dll or do I have to remake the dlls
with some option?

-----Original Message-----
From: Bernard Delm�e [mailto:bdelmee@advalvas.ZAPME.be]
Sent: Sunday, December 23, 2001 3:18 PM
To: ruby-talk ML; undisclosed-recipients:
Subject: [ruby-talk:29382] Re: x.dll versus x.lib in mswin32 ruby


> Does this mean that I cannot use DLL's in mswin32 Ruby?  This doesn't make
> any sense.

Naturally you can; DLL's are used at run-time (and hold the actual code),
whereas LIB's are used at build/link time (and only hold relocation info).
This is similar to .so vs .a on *nix.

HTH.