[vtk-developers] Module interface files

[David Gobbi]

Why can't paraview be made to check the WRAP_EXCLUDE
property for each file?  Adding another list seems messy.

 - David

On Mon, Oct 29, 2012 at 1:15 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Oh! Yea, I'd think that can be fixed. We cannot simply extend the same
> list though (since ParaView depends on that now), but I vote for
> adding another variable.
>
> Utkarsh
>
> On Mon, Oct 29, 2012 at 3:12 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>> Hi Utkarsh,
>>
>> That is the file that I was referring to.  It only lists classes
>> that are not WRAP_EXCLUDE.  In contrast, the VTK 5.10
>> Kit.cmake files listed all the classes, not just wrapped ones.
>>
>>  - David
>>
>> On Mon, Oct 29, 2012 at 1:07 PM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>> There is a separate Module-Classes.cmake file that's written out that
>>> has all the classes.
>>>
>>> On Mon, Oct 29, 2012 at 2:16 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>>>> The module API files installed in lib/cmake/vtk-6.0/Modules
>>>> only list classes that aren't marked WRAP_EXCLUDE.  This
>>>> is different from the behavior of VTK 5, which listed all classes.
>>>> Is there a reason for this change?
>>>>
>>>> I'd prefer if all the classes were listed, with wrap-excluded files
>>>> marked as WRAP_EXCLUDE in the file.
>>>>
>>>>  - David