[Swig-user] Controlling #include

[Robert J. <rob...@gm...>]

I'm sure this must have come up before, but is there any way to exercise
a bit more control over whether Swig follows #includes.

At present I understand Swig does not follow #include at all, unless you
specify -includeall on the command line. It would be lovely to be able to
give
Swig a list of directories in the style of -I<dir>, and then say follow
#includes
if and only if the file to be included resides in one of the listed
directories.

This would allow Swig to automatically wrap everything defined in my
own headers, but not wrap all the system stuff.

Any thoughts gentlemen?

Rob