This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: stdcall, @s, and ld/dlltool...
- From: Matthew Brett <matthew dot brett at mrc-cbu dot cam dot ac dot uk>
- To: Dmitry Timoshkov <dmitry at baikal dot ru>
- Cc: Matthew Brett <matthew dot brett at mrc-cbu dot cam dot ac dot uk>, binutils at sources dot redhat dot com
- Date: Tue, 25 Dec 2001 13:51:42 +0000 (GMT)
- Subject: Re: stdcall, @s, and ld/dlltool...
Dear Dmitri,
> Some time ago I had a similar problem. With the help from
cygwin and binutils
> mailing lists, I've got the following:
>
> I was using the following command lines to build DLLs:
>
> dllwrap -o $(LIBRARY).dll $(OBJS) $(LIBS) -k --def $(LIBRARY).def
-Wl,--kill-at,--enable-stdcall-fixup
> dlltool --kill-at --input-def $(LIBRARY).def --output-lib lib$(LIBRARY).a
Many thanks for the reply. Suffering as I have from this problem, I had
found your messages on this list, which was why I reposted here. I have
the painful feeling I don't understand this problem completely, but my
worry is that I can't use this solution:
> dllwrap -o $(LIBRARY).dll $(OBJS) $(LIBS) -k --def $(LIBRARY).def ...
because I do not have the source for the libraries. It is true isn't it
that for some reason --enable-stdcall-fixup when doing final linking with
the dll library created by dlltool, does not work on this problem? Is
this a bug?
Many thanks again - and happy Xmas!
Matthew