[vtk-developers] Wrapping/Tools

[Marcus D. Hanwell]

Ideally a module would not affect how any other module is built. If
you need to do it then we provide ${vtk-module}_ENABLED, so
vtkWrappingTools_ENABLED should be checked, if it is true the module
has been enabled.

Marcus

On Thu, Aug 16, 2012 at 1:52 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> Just one more quick question before I push the next (hopefully final) changeset.
>
> How can I force vtkWrapping.cmake to build the hierarchy files
> whenever the vtkWrappingTools module is on?  What is the best way in
> cmake to check if a module has been turned on?  Or is it even a wise
> thing to do?
>
>  - David
>
>
> On Thu, Aug 16, 2012 at 10:49 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Hmm, in that case I'd vote for building those always. These are just
>> build tools like vtkProcessShader, etc, which are always built whether
>> they are used or not. Makes it possible for projects dependent on VTK
>> to wrap their own classes in Python etc even if VTK was not Python
>> wrapped, for example.
>>
>> Utkarsh
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>