File tree Expand file tree Collapse file tree 1 file changed +5
-0
lines changed Expand file tree Collapse file tree 1 file changed +5
-0
lines changed Original file line number Diff line number Diff line change @@ -9062,6 +9062,11 @@ <H3><a name="Java_using_own_jni_functions">27.12.3 Using your own JNI functions<
9062
9062
Here the default typemaps work for < tt > int</ tt > and < tt > char *</ tt > .
9063
9063
</ p >
9064
9064
9065
+ < p >
9066
+ Note that if you're wanting to effectively < b > replace</ b > the JNI code generated for a C/C++ function then you'll need to use < tt > %ignore</ tt > as well
9067
+ to tell SWIG not to automatically generate a JNI wrapper for it.
9068
+ </ p >
9069
+
9065
9070
< p >
9066
9071
In summary the < tt > %native</ tt > directive is telling SWIG to generate the Java code to access the JNI C code, but not the JNI C function itself.
9067
9072
This directive is only really useful if you want to mix your own hand crafted JNI code and the SWIG generated code into one Java class or package.
You can’t perform that action at this time.
0 commit comments