[vtk-developers] vtkImageReader2Factory missing in VTK modular

[Bill Lorensen]

I'll check into the AutoInit code.

On Fri, Apr 13, 2012 at 4:32 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> I checked the SQL AutoInit code and it seems to be right mechanism to
> use.   The IOMINC module is a logic place to try it out.
>
> For polydata, where the readers are spread among a large number of
> modules, each module that contains readers would need to contain an
> AutoInit class.  It would be a bit repetitive, but I think it's the
> right way to go.
>
> The factory-in-its-own-module approach would mean that building the
> factory would require building ALL the modules that contain readers,
> which is something I don't really like.
>
>  - David
>
>
> On Fri, Apr 13, 2012 at 2:23 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> David,
>> Runtime registration for MINC seems like the right way top go. Another
>> possibility is to put the factory in its own module, since in the
>> future other image readers might be added that have unusual
>> dependencies.
>>
>> I am working on a polydata reader factory that will probably have
>> unusual depdendices (its abandoned until I get a chance to rebase on
>> modular).
>>
>> Bill
>>
>> On Fri, Apr 13, 2012 at 4:06 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>>> On Fri, Apr 13, 2012 at 12:47 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>>>> vtkImageReader2Factory is in IO/Image but is commented out of the
>>>> CMakeLists.txt. I tried uncommenting but it needs IO/MINC and when I
>>>> add that dependency it causes a circular dependency.
>>>
>>> In the long term, it might be necessary to have vtkMINCReader register
>>> itself with the factory at run-time.  The temporary fix would be to simply
>>> add "#if 0" blocks around all vtkImageReader2Factory.cxx code that
>>> needs vtkMINCReader. That will at least allow the factory to be compiled.
>>>
>>>  - David



-- 
Unpaid intern in BillsBasement at noware dot com