[Paraview-developers] AUTOLOAD option is deprecated in ParaView 3.98 RC2
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Wed Nov 14 10:36:03 EST 2012
Cory,
We need to write a migration guide, I am going to try to put something
together soon. However, AUTOLOAD should have not have mattered much for
plugins that are built outside ParaView. If I remember correctly, AUTOLOAD
only affected the state of the "autoload" flag in the .plugins
configuration file while is only built for plugins included in ParaView
source. For any plugin that the users load manually, they can turn on
autoloading from the GUI, in any case.
For plugins built outside ParaView, you shouldn't use pv_plugin(). That
mechanism is only for plugins included in the ParaView source.
Utkarsh
On Tue, Nov 13, 2012 at 7:40 AM, Cory Quammen <cquammen at cs.unc.edu> wrote:
> I have a ParaView plugin that uses the AUTOLOAD option in a call to
> add_paraview_plugin(). Compiling against ParaView 3.98 RC2, I get the
> following message:
>
> CMake Warning at
>
> /Users/quammen/dev/madai/build/MADAIWorkbench-ParaViewTracking-Debug/src/ParaView/CMake/ParaViewPlugins.cmake:1009
> (message):
> AUTOLOAD option is deprecated. Plugins built within ParaView source
> should
> use pv_plugin(..) macro with AUTOLOAD argument.
>
> This is a plugin built outside ParaView source, so should I use
> pv_plugin()? Is this change documented in a ParaView migration guide?
>
> Thanks,
> Cory
> _______________________________________________
> 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/20121114/dfe8eb88/attachment-0001.htm>
More information about the Paraview-developers
mailing list