[vtkusers] Python no vtkVolumeTextureMapper3D

[Shawn Waldon]

I have always found it safest when switching rendering backends to have
separate build trees.  The wrappers will get confused otherwise.  Even make
clean doesn't really help with this.

Shawn

On Wed, Apr 8, 2015 at 9:32 AM, David Lonie <david.lonie at kitware.com> wrote:

> On Tue, Apr 7, 2015 at 2:22 PM, Windes, Grant <
> Grant.Windes at smith-nephew.com> wrote:
>
>>  Oddly, I had enabled the rendering_backend to opengl2 but I reverted
>> that back to opengl. Not sure why it still caused it to not build the
>> textureMapper3D. Is there a way to see which rendering engine is actually
>> being used via python?
>>
>
> I've noticed something similar regarding modules and the wrapping code.
> The wrappers don't always seem to update when modules are enabled/disabled
> between incremental builds. For instance, I have a branch that removes the
> vtkRenderingFreeTypeOpenGL module here:
>
> https://gitlab.kitware.com/paraview/paraview/merge_requests/1
>
> and it's spawning a lot of errors like:
>
> https://open.cdash.org/testDetails.php?test=320681415&build=3756410
>
> Even though the module is disabled (removed, actually), the wrapper
> initialization still tries to load it. Looks like some of the init scripts
> are missing dependencies?
>
> Might be related to switching between the OpenGL backend modules.
>
> Dave
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Search the list archives at: http://markmail.org/search/?q=vtkusers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20150408/111d5257/attachment.html>