[Swig-user] How to #include your own header before the #includes that swig generates?

[Alan W. I. <ir...@be...>]

The vanilla octave header, /usr/include/octave/oct-dlldefs.h, doesn't
handle gcc visibility at all.  To correct that issue the PLplot
developers would like to replace

#define OCTAVE_EXPORT

set unconditionally in the above header with

#define OCTAVE_EXPORT __attribute__ ( ( visibility( "default" ) ) )

when gcc is being used for the compiler.

In order for that idea to work, our modified oct-dlldefs.h header must
be #included before the octave-related #include statements generated
by swig, e.g.,

#include <octave/oct.h>
#include <octave/parse.h>
#include <octave/ov-fcn-handle.h>
#include <octave/Cell.h>
#include <octave/oct-map.h>

The first few lines of our current plplot_octave.i file are

%module plplot_octave

%{
#include "plplotP.h"
%}

but we notice the resulting #include statement occurs after the above #includes
in the generated source code.

Is there some swig directive or other swig method which will allow us
to #include our own octave-related header before the above #includes which are
generated by swig?

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________