From: Borneq <borucki.andrzej@gmail.com>
To: java@gcc.gnu.org
Subject: Not add leading underscore in function name in DLL
Date: Wed, 04 Sep 2013 19:53:00 -0000 [thread overview]
Message-ID: <1378324424834-965830.post@n5.nabble.com> (raw)
I try make Java native function by JNI.
I have in Java code:
package net.sf.junace;
public class UnACE {
native void nativeACEList(String ArchiveName, ACEList struct);
}
javah make in net_sf_junace_UnACE.h :
JNIEXPORT void JNICALL Java_net_sf_junace_UnACE_nativeACEList
when compile by Visual C++, it add leading underscore to function name :
_Java... and it is OK, but when compile with GCC it not add.
I try use option "-Wl,--kill-at" but this not helps.
I don't want change *.h file because it is autogenerated.
--
View this message in context: http://gcc.1065356.n5.nabble.com/Not-add-leading-underscore-in-function-name-in-DLL-tp965830.html
Sent from the gcc - java mailing list archive at Nabble.com.
reply other threads:[~2013-09-04 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1378324424834-965830.post@n5.nabble.com \
--to=borucki.andrzej@gmail.com \
--cc=java@gcc.gnu.org \
/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).