public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Find dll name corresponding to an import library
@ 2013-11-06 22:35 Jean-Pierre Flori
  2013-11-07  1:46 ` Warren Young
  2013-11-07  4:04 ` Charles Wilson
  0 siblings, 2 replies; 5+ messages in thread
From: Jean-Pierre Flori @ 2013-11-06 22:35 UTC (permalink / raw)
  To: cygwin

Dear all,

Is there a canonical way to do so?

Best,
JP


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Find dll name corresponding to an import library
  2013-11-06 22:35 Find dll name corresponding to an import library Jean-Pierre Flori
@ 2013-11-07  1:46 ` Warren Young
  2013-11-07  1:50   ` Warren Young
  2013-11-07  4:04 ` Charles Wilson
  1 sibling, 1 reply; 5+ messages in thread
From: Warren Young @ 2013-11-07  1:46 UTC (permalink / raw)
  To: Cygwin-L

On 11/6/2013 15:31, Jean-Pierre Flori wrote:
>
> Is there a canonical way to do so?

The canonical way is to name your import libraries so that the name of 
the corresponding DLL is obvious.

Non-Cygwin import libraries are traditionally named after the DLL: 
foo.lib is for foo.dll.

Cygwin's stock build system is a bit different, due to POSIX naming 
norms, but the transform is simple: libfoo.a is for cygfoo.dll.

If you have an import library with a name that doesn't conform to one of 
these schemes, you might be able to dig the DLL name out of the library 
file.  Through some futzing around, I've discovered that this works:

     $ objdump -s foo.a | grep cyg.*dll$

That assumes that the DLL uses the "cyg" prefix.  Just grepping for 
"dll$" would be a better option if you weren't sure about even that.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Find dll name corresponding to an import library
  2013-11-07  1:46 ` Warren Young
@ 2013-11-07  1:50   ` Warren Young
  0 siblings, 0 replies; 5+ messages in thread
From: Warren Young @ 2013-11-07  1:50 UTC (permalink / raw)
  To: Cygwin-L

On 11/6/2013 18:46, Warren Young wrote:
> libfoo.a is for cygfoo.dll.

Sorry, that should be "libfoo.dll.a is for cygfoo*.dll, where the 
wildcard may be replaced by some extra version information".  Use the 
objtool command to narrow things down if there are multiple candidates.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Find dll name corresponding to an import library
  2013-11-06 22:35 Find dll name corresponding to an import library Jean-Pierre Flori
  2013-11-07  1:46 ` Warren Young
@ 2013-11-07  4:04 ` Charles Wilson
  2013-11-07 21:50   ` Jean-Pierre Flori
  1 sibling, 1 reply; 5+ messages in thread
From: Charles Wilson @ 2013-11-07  4:04 UTC (permalink / raw)
  To: cygwin

On 11/6/2013 5:31 PM, Jean-Pierre Flori wrote:
> Is there a canonical way to do so?

dlltool --identify libfoo.a

--
Chuck


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Find dll name corresponding to an import library
  2013-11-07  4:04 ` Charles Wilson
@ 2013-11-07 21:50   ` Jean-Pierre Flori
  0 siblings, 0 replies; 5+ messages in thread
From: Jean-Pierre Flori @ 2013-11-07 21:50 UTC (permalink / raw)
  To: cygwin

Le Wed, 06 Nov 2013 23:04:26 -0500, Charles Wilson a écrit :

> On 11/6/2013 5:31 PM, Jean-Pierre Flori wrote:
>> Is there a canonical way to do so?
> 
> dlltool --identify libfoo.a

Thanks that's exactly what I wanted and seems cleaner than using objdump!


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-11-07 21:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-06 22:35 Find dll name corresponding to an import library Jean-Pierre Flori
2013-11-07  1:46 ` Warren Young
2013-11-07  1:50   ` Warren Young
2013-11-07  4:04 ` Charles Wilson
2013-11-07 21:50   ` Jean-Pierre Flori

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).