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.
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:
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 repo
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 sto
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
5 matches
Mail list logo