[Paraview] VTK_IO_EXPORT vs VTK_EXPORT (VTK_ABI_IMPORT vs VTK_ABI_EXPORT)

[Marcus D. Hanwell]

On Sat, Apr 16, 2011 at 9:04 PM, Xunlei Wu <xunlei at renci.org> wrote:
> Thanks a lot, Marcus.
> I was hoping to figure out why my plugin dll does not behave the same way as other internally built reader classes (dlls) which have the clause of dllexport and dllimport depending on the hosting project. My plugin dll only specifies dllexport as instructed by ParaView plugin examples. These internal readers can populate "Cell/Point Array Status" list in the "Object Inspector" widget -> "Properties" panel, whereas my reader plugin cannot. Following vtkAVSucdReader.h/cxx does not work yet. Any hint? Sorry for the divergence of the topic. My real problem has been posted in
> http://www.paraview.org/pipermail/paraview/2011-March/020696.html
>
I don't think it is a symbol visibility issue, but couldn't really
comment beyond that. Plugins are not built against, and so do not
require the dllimport logic.

Marcus