This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: RESOLVED: Using gcc to build a DLL discovered and linked at runtime
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 17 Jan 2003 11:05:23 -0500
- Subject: Re: RESOLVED: Using gcc to build a DLL discovered and linked at runtime
- References: <20030117145817.95468.qmail@web20002.mail.yahoo.com>
- Reply-to: cygwin at cygwin dot com
On Fri, Jan 17, 2003 at 06:58:17AM -0800, Joshua Daniel Franklin wrote:
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>
>References: <3E2753C9.4040008@kleckner.net>, <3E25A7EE.7050109@kleckner.net>
>
>> After carefully inspecting the symbols from
>> generated dlls and dlls provided by TradeStation,
>> I found that symbols occurred with and without the
>> @decorations. e.g. PPI@4 and PPI.
>>
>> Adding -Wl,--add-stdcall-alias to the gcc line,
>> all worked fine.
>>
>> Could this generally be a requirement for dlls
>> that are opened at runtime in a fashion similar to
>> dlopen? If so, then some FAQ annotation would be
>> in order here:
>> http://www.cygwin.com/cygwin-ug-net/dll.html
>
>I may be wrong (I'm not a GCC expert), but isn't that more
>of a gcc thing than a cygwin thing?
>
>I don't want to end up pasting the whole gcc manual into
>the "Using DLLs" page. It's really only intended to be a quick
>start for cygwin, not a comprehensive guide.
Right. The --add-stdcall-alias option is also not something
that you just nonchantly add to the command line. It does not
belong in a general guide, except, perhaps as a q.v.
cgf
--
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/