Use the system angle brackets for %include
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@7871 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
55a48adb5b
commit
cfdad24993
52 changed files with 132 additions and 134 deletions
|
|
@ -7,7 +7,7 @@
|
|||
Example usage:
|
||||
Wrapping:
|
||||
|
||||
%include "arrays_java.i"
|
||||
%include <arrays_java.i>
|
||||
%inline %{
|
||||
short FiddleSticks[3];
|
||||
%}
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
* ----------------------------------------------------------------------------- */
|
||||
|
||||
|
||||
%include "javahead.swg"
|
||||
%include <javahead.swg>
|
||||
|
||||
/* The jni, jtype and jstype typemaps work together and so there should be one of each.
|
||||
* The jni typemap contains the JNI type used in the JNI (C/C++) code.
|
||||
|
|
@ -1192,8 +1192,8 @@ SWIG_PROXY_CONSTRUCTOR(true, true, SWIGTYPE)
|
|||
%apply unsigned long { size_t };
|
||||
|
||||
/* java keywords */
|
||||
%include "javakw.swg"
|
||||
%include <javakw.swg>
|
||||
|
||||
// Default enum handling
|
||||
%include "enumtypesafe.swg"
|
||||
%include <enumtypesafe.swg>
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,8 @@
|
|||
//
|
||||
// Common implementation
|
||||
|
||||
%include std_common.i
|
||||
%include exception.i
|
||||
%include <std_common.i>
|
||||
%include <exception.i>
|
||||
|
||||
// ------------------------------------------------------------------------
|
||||
// std::pair
|
||||
|
|
|
|||
|
|
@ -44,12 +44,12 @@ To use these, suppose you had a C function like this :
|
|||
|
||||
You could wrap it with SWIG as follows :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
double fadd(double *INPUT, double *INPUT);
|
||||
|
||||
or you can use the %apply directive :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply double *INPUT { double *a, double *b };
|
||||
double fadd(double *a, double *b);
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ In Java you could then use it like this:
|
|||
double answer = modulename.fadd(10.0, 20.0);
|
||||
|
||||
There are no char *INPUT typemaps, however you can apply the signed char * typemaps instead:
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply signed char *INPUT {char *input};
|
||||
void f(char *input);
|
||||
*/
|
||||
|
|
@ -174,12 +174,12 @@ returns the integer part in one of its parameters):
|
|||
|
||||
You could wrap it with SWIG as follows :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
double modf(double x, double *OUTPUT);
|
||||
|
||||
or you can use the %apply directive :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply double *OUTPUT { double *ip };
|
||||
double modf(double x, double *ip);
|
||||
|
||||
|
|
@ -190,7 +190,7 @@ value in the single element array. In Java you would use it like this:
|
|||
double fraction = modulename.modf(5.0,ptr);
|
||||
|
||||
There are no char *OUTPUT typemaps, however you can apply the signed char * typemaps instead:
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply signed char *OUTPUT {char *output};
|
||||
void f(char *output);
|
||||
*/
|
||||
|
|
@ -310,12 +310,12 @@ For example, suppose you were trying to wrap the following function :
|
|||
|
||||
You could wrap it with SWIG as follows :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
void neg(double *INOUT);
|
||||
|
||||
or you can use the %apply directive :
|
||||
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply double *INOUT { double *x };
|
||||
void neg(double *x);
|
||||
|
||||
|
|
@ -332,7 +332,7 @@ languages in that other languages will return the output value as part
|
|||
of the function return value. This difference is due to Java being a typed language.
|
||||
|
||||
There are no char *INOUT typemaps, however you can apply the signed char * typemaps instead:
|
||||
%include "typemaps.i"
|
||||
%include <typemaps.i>
|
||||
%apply signed char *INOUT {char *inout};
|
||||
void f(char *inout);
|
||||
*/
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue