[vtk-developers] NULL always returned from vtkPolyDataMapper::New()
Kyle Lutz
kyle.lutz at kitware.com
Fri Nov 16 13:57:04 EST 2012
That was the link I needed!
This was the wiki page I was going off of:
http://www.vtk.org/Wiki/VTK/VTK_6_Migration_Guide and I didn't see
anything about CMake/compiling/linking changes. I think adding that
link to the list would be very helpful. Perhaps break the list into
sections like C++ code changes, Python code changes, Build system
changes, etc..
Thanks,
Kyle
On Fri, Nov 16, 2012 at 10:50 AM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> On Mon, Nov 12, 2012 at 5:45 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> Because of the new factory mechanism in vtk6 you need to
>> #include "vtkRenderingOpenGL.h"
>
> You don't need to do that, so long as you include a header from the
> interface module (in this case vtkRenderingCore) that module's header
> will ensure the factory for all implementation modules are
> initialized. See,
>
> http://vtk.org/Wiki/VTK/Build_System_Migration#Implementation_Modules
>>
>> also
>> in your CmakeLists.txt file don't add include_directories, just
>> include(${VTK_USE_FILE})
>>
>> and for the libraries use
>> ${VTK_LIBRARIES}
>>
> http://vtk.org/Wiki/VTK/Build_System_Migration#Finding_and_Linking_to_VTK
> documents how to find/link to the new VTK modules. I will try to find
> the right place to link to this page from the VTK wiki front page too,
> as I just realized I had not done that.
>
> Marcus
More information about the vtk-developers
mailing list