RE: help with using windows dll

RE: help with using windows dll

[Heribert Dahms]

Hi Frank,

BTW, please fix your mail settings
to use the correct charset=iso-8859-1
since iso_8859_1 is invalid!

Bye, Heribert (heribert_dahms@icon-scm.com)

> -----Original Message-----
> From:	Frank Motta [SMTP:fmotta@embedded-guru.com]
> Sent:	Wednesday, April 10, 2002 22:35
> To:	gp@familiehaase.de
> Cc:	cygwin@cygwin.com
> Subject:	Re: help with using windows dll
> 
> This message uses a character set that is not supported by the Internet
> Service.  To view the original message content,  open the attached
> message. If the text doesn't display correctly, save the attachment to
> disk, and then open it using a viewer that can display the original
> character set. << File: message.txt >> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: help with using windows dll

[Frank Motta]

WOW!!!
Thanks!!!
this is great!!!
I've installed and run it and (visually) it appears to give me
what I need - the next test is (of course) link and run :}

<Gerrit P. Haase>
>> -------- Original Message --------
>> Subject: =?iso_8859_1?Q?can_a_pre-built_library_be_used=3F?=
>> From: "Frank Motta" <fmotta at embedded-guru dot com>
>> To: <cygwin at cygwin dot com>
>
>> I have a third party lib/dll (x.lib, x.dll) built with microsoft tools
>> I need to link to a cygwin application.
>
>> Since cygwin can't use the .lib then is there a way of extracting the
>> equivilent stubs from the .lib or the dll?
>
>>     Is this possible?
>
>>     If so, how!!!
>
> I used to do this with a tool that comes with libtool.
> It isn't provided in binary form with the libtool setup,
> but gets build everytime it is needed by libtool.
> I've it on a website to fetch it for others (just the
> C source and the compiled binary).
>
> I use it with this stupid script which is invoked like this,
>
>        $ libextract /path/DLLNAME
>
> where DLLNAME is the dllname without .dll:
>
> #!/usr/bin/sh
> echo $0 creates import library $1.dll.a from $*.dll
> DLLNAME=$@
>
> /bin/impgen ${DLLNAME}.dll >${DLLNAME}.def
> dlltool --as=as --dllname ${DLLNAME}.dll --def ${DLLNAME}.def
> --output-lib ${DLLNAME}.dll.a # ENDE
>
> Extract the 'impgen' source from ltmain.sh or fetch it here:
> http://timtowtdi.topcities.com/cygwin/impgen/
>
> My script needs some improvements since importlibraries are usually
> named in another fashion.  Here cygbz21.0.dll gets cygbz21.0.dll.a as
> importlib where the real one is named libbz2.dll.a.
> But you can either link directely to the name you created the importlib
> with or rename it as you like it.
>
> Also I should mention that it works with some Windows dll's and with
> others it doesn't work and I don't know why.
>
>
> Gerrit
> --
> =^..^=


-- 
Frank Motta
fmotta@embedded-guru.com

If you cannot recognize divinity in your fellow man, then you will not
realize the devine within yourself...





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: help with using windows dll

[Gerrit P. Haase]

> -------- Original Message --------
> Subject: =?iso_8859_1?Q?can_a_pre-built_library_be_used=3F?=
> From: "Frank Motta" <fmotta at embedded-guru dot com>
> To: <cygwin at cygwin dot com>

> I have a third party lib/dll (x.lib, x.dll) built with microsoft tools
> I need to link to a cygwin application.

> Since cygwin can't use the .lib then is there a way of extracting the
> equivilent stubs from the .lib or the dll?

>     Is this possible?

>     If so, how!!!

I used to do this with a tool that comes with libtool.
It isn't provided in binary form with the libtool setup,
but gets build everytime it is needed by libtool.
I've it on a website to fetch it for others (just the
C source and the compiled binary).

I use it with this stupid script which is invoked like this,

        $ libextract /path/DLLNAME

where DLLNAME is the dllname without .dll:

#!/usr/bin/sh
echo $0 creates import library $1.dll.a from $*.dll
DLLNAME=$@

/bin/impgen ${DLLNAME}.dll >${DLLNAME}.def
dlltool --as=as --dllname ${DLLNAME}.dll --def ${DLLNAME}.def --output-lib ${DLLNAME}.dll.a
# ENDE

Extract the 'impgen' source from ltmain.sh or fetch it here:
http://timtowtdi.topcities.com/cygwin/impgen/

My script needs some improvements since importlibraries are usually
named in another fashion.  Here cygbz21.0.dll gets cygbz21.0.dll.a as
importlib where the real one is named libbz2.dll.a.
But you can either link directely to the name you created the importlib
with or rename it as you like it.

Also I should mention that it works with some Windows dll's and with
others it doesn't work and I don't know why.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

help with using windows dll

[Frank Motta]

-------- Original Message --------
Subject: =?iso_8859_1?Q?can_a_pre-built_library_be_used=3F?=
From: "Frank Motta" <fmotta@embedded-guru.com>
To: <cygwin@cygwin.com>

I have a third party lib/dll (x.lib, x.dll) built with microsoft tools
I need to link to a cygwin application.

Since cygwin can't use the .lib then is there a way of extracting the
equivilent stubs from the .lib or the dll?

    Is this possible?

    If so, how!!!


    thanks!
-- 
Frank Motta
fmotta@embedded-guru.com

If you cannot recognize divinity in your fellow man, then you will not
realize the devine within yourself...


-- 
Frank Motta
fmotta@embedded-guru.com

If you cannot recognize divinity in your fellow man, then you will not
realize the devine within yourself...





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/