[vtk-developers] Python Changes

[Ben Boeckel]

On Mon, Dec 18, 2017 at 10:31:50 -0500, Ken Martin wrote:
> Maybe someone changed something in the python wrapping/build resulting in
> these warnings?

Yeah, wrappers are now trying to wrap "everything". Though currently
there is no real indication of what is public API and private API, so
private APIs may get wrapped up unintentionally.

When I removed EXCLUDE_WRAP, I hid the headers which the wrappers
actively failed on. In order to hide these headers (which seem to be
private), you can wrap them in:

    #ifndef __VTK_WRAP__
    #endif

If they also have headers which don't work from the wrappers (not true
if they're working now, but for future cases), also add:

    #ifndef VTK_WRAPPING_CXX
    #endif

to hide it from the "no-op" wrapper source as well. These will disappear
with the new module system since these headers are private and shouldn't
be looked at by wrapper tools at all.

--Ben