[Sablevm-bugs] [ sablevm-Bugs-981658 ] jni.h should use JNIIMPORT, not JNIEXPORT
Brought to you by:
egagnon
From: SourceForge.net <no...@so...> - 2004-07-03 21:12:55
|
Bugs item #981658, was opened at 2004-06-28 19:53 Message generated for change (Comment added) made by egagnon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105523&aid=981658&group_id=5523 Category: Other Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Tom Schutter (tschutter) Assigned to: Nobody/Anonymous (nobody) Summary: jni.h should use JNIIMPORT, not JNIEXPORT Initial Comment: In jni.h, the prototypes for functions such as JNI_CreateJavaVM() should be using JNIIMPORT, not JNIEXPORT. Although JNIEXPORT is an empty define on Linux, on platforms such as Windows it is defined. If an app needs to define a function pointer type for JNI_CreateJavaVM(), it needs the JNIIMPORT variant, not the JNIEXPORT variant. ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-07-03 17:12 Message: Logged In: YES user_id=15365 This bug has been moved to the new SableVM Bug Tracking System. Please visit: http://sablevm.org/bugs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105523&aid=981658&group_id=5523 |