[Paraview-developers] static build and shared library plugins

[David E DeMarle]

Sounds great - as long as one side of the option keeps the enabled plugins
baked in the way they are now for those few remaining and exceedingly lame,
platforms that have no support for dynamic loading at all.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Apr 16, 2014 at 3:33 PM, Andy Bauer <andy.bauer at kitware.com> wrote:

> I'm in favor of this. The streaming particles plugin is the latest to
> cause me some grief for cross-compiled static builds on a Cray with the
> exact behavior you mentioned (crashing at the first render).
>
>
> On Wed, Apr 16, 2014 at 3:29 PM, Burlen Loring <burlen.loring at gmail.com>wrote:
>
>> Hi All,
>>
>> How would you feel about a build option that will allow normal shared
>> library based, run time loaded, plugins when PV is built with
>> BUILD_SHARED_LIBS=OFF?
>>
>> The reason I'm interested is that static link handling of plugins are
>> currently the remaining obstacle to deploying static library based PV at
>> NERSC. We need the static library build for performance reasons at the same
>> time various users have request plugins. Recent versions of VTK supported
>> python and static library build, yay! plugins are the remaining issue.
>>
>> Burlen
>>
>> for context here's a recap of static build plugin issues, when the
>> plugins are baked into the server:
>>
>> 1) upon job startup users are confronted with a complicated pop up dialog
>> through which they must then load all of the missing plugins, else PV
>> crashes on the first render.
>>
>> 2) some of the plugins change the GUI when loaded
>>
>> both are confusing for many users
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20140416/1c1413c7/attachment.html>