Re: octave - vtk

[Levente Torok]

2010/11/4 Jordi Gutiérrez Hermoso <address@hidden>:
> Would you rather keep this public? I know this isn't about Octave, but
> maybe they'll let us discuss this publicly before they yell at us. ;-)
>
> 2010/11/4 Levente Torok <address@hidden>:
>> I wanted to do the compilation but I got stuck.
>> First with type redefinition of  vtkIdType in place of int's in function
>> octaviz/Common/vtkIdTypeArray.cc: In function ‘octave_value_list
>> FvtkIdTypeArray(const octave_value_list&, int)’:
>> I replaced them and did some casting at return types so now it compiles.
>
> I don't know what the right way to fix it is, but I know that's not it.
>
> See, the way VTK wrapping works is that those files are automatically
> generated by the parser/lexer files. If you look at the Octaviz
> distribution, you'll see that those .cc files that you patched are not
> there.
>
> What we need to do is figure out how types may have changed in a newer
> release of VTK and patch the parser and lexer accordingly. I don't
> know enough about parsers and lexers to do this. I'm now reading about
> compiler design looking for insight.
>
> Sorry,
> - Jordi G. H.
>

Hi Jordi,

Sure we can keep it public. I just didn't want to bother all of those
who are not really interested in the parts.
So I have no clue where to step with this either.

Lev