From: Mumit Khan <khan@xraylith.wisc.edu>
To: Andrew Mickish <mickish@cmu.edu>
Cc: Glen Fullmer-EGF002 <Glen_Fullmer-EGF002@email.mot.com>,
gnu-win32@cygnus.com
Subject: Re: dll, java, gcc, cygwin
Date: Sat, 24 Oct 1998 14:15:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.981024160951.23565A-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <362F5356.36BA95C0@cmu.edu>
On Thu, 22 Oct 1998, Andrew Mickish wrote:
> It might be related to name mangling. Try adding .def aliases in your larger
> example. I have to supply aliases in a .def file like the following for every native
> method I export from the DLL:
>
> EXPORTS
> Java_HelloWorld_displayHelloWorld=Java_HelloWorld_displayHelloWorld@8
> dll_entry@12
>
Here's a proposal: how about I add a --add-stdcall-alias to dlltool which
essentially produce the following:
EXPORTS
Java_HelloWorld_displayHelloWorld=Java_HelloWorld_displayHelloWorld@8
Java_HelloWorld_displayHelloWorld@8
When creating .def file using ``dlltool --output-def''. Would this solve
the problem? Note that I'm keeping the original symbol as well, but we
could always get rid of that too.
Making DLLs then look like the following:
dlltool --output-def my.def --add-stdcall-alias [ ... ] *.o
dllwrap -o my.dll --def my.def [ .... ]*.o
btw, you should *never* export DLL entry points (unless you really know
what you're doing of course).
Regards,
Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1998-10-24 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-21 10:06 Glen Fullmer-EGF002
1998-10-23 0:05 ` Andrew Mickish
1998-10-24 14:15 ` Mumit Khan [this message]
1998-10-23 6:03 ` Mumit Khan
1998-10-24 3:21 ` Glen Fullmer-EGF002
1998-10-23 23:07 Philip A. Larson
1998-10-24 10:29 ` John A. Turner
1998-10-25 6:39 Earnie Boyd
1998-10-25 9:45 ` Mumit Khan
1998-10-25 20:17 Philip A. Larson
[not found] <Pine.SUN.3.93.981026173739.25460B-100000@modi.xraylith.wisc.edu>
1998-10-26 16:05 ` Glen Fullmer-EGF002
1998-10-28 0:40 Earnie Boyd
1998-10-27 15:02 ` Mumit Khan
1998-10-29 8:16 ` Glen Fullmer-EGF002
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.93.981024160951.23565A-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=Glen_Fullmer-EGF002@email.mot.com \
--cc=gnu-win32@cygnus.com \
--cc=mickish@cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).