[vtk-developers] Wrapping/Tools

David Gobbi david.gobbi at gmail.com
Thu Aug 16 12:45:04 EDT 2012


Then I'll have to change this conditional in Wrapping/Tools/CMakeLists.txt:

  if(VTK_WRAP_TCL OR VTK_WRAP_PYTHON OR VTK_WRAP_JAVA OR VTK_GENERATE_WRAPTOOLS)
    add_executable(vtkWrapHierarchy vtkWrapHierarchy.c)
    target_link_libraries(vtkWrapHierarchy vtkWrappingTools)
    vtk_compile_tools_target(vtkWrapHierarchy)
  endif()

The vtkWrapHierarchy tool can just be built whenever the module is on.

In fact there isn't any reason to conditionally build any of the
wrapper tools.  The vtkWrapPython executable doesn't need vtkPython.h
or the python libs anymore, and vtkWrapTcl/Java never required Tcl or
Java.

 - David


On Thu, Aug 16, 2012 at 10:25 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Dave,
>
> I think we can get rid of the VTK_GENERATE_WRAPTOOLS. ParaView should
> be able to just enable the vtkWrappingTools module on its own now that
> it's a legitimate module. In fact, vtkClientServerWrapping can
> COMPILE_DEPENDS on it too and we'll be all set there.
>
> Utkarsh
>
> On Thu, Aug 16, 2012 at 11:13 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>> The WrappingTools module is ready:
>> http://review.source.kitware.com/#/t/859/
>>
>> I have added "COMPILE_DEPENDS vtkWrappingTools" to the
>> vtkWrappingPython, vtkWrappingJava, and vtkWrappingTcl modules,
>> as Marcus recommended.
>>
>> One thing I wasn't sure about was what to do with
>> VTK_GENERATE_WRAPTOOLS.  Utkarsh, can you check my changes
>> to the main CMakeLists.txt to see if I am doing the right thing?
>>
>>  - David



More information about the vtk-developers mailing list