Cory,<div><br></div><div>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. </div>
<div><br></div><div>For plugins built outside ParaView, you shouldn't use pv_plugin(). That mechanism is only for plugins included in the ParaView source.</div><div><br></div><div>Utkarsh</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 7:40 AM, Cory Quammen <span dir="ltr"><<a href="mailto:cquammen@cs.unc.edu" target="_blank">cquammen@cs.unc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a ParaView plugin that uses the AUTOLOAD option in a call to<br>
add_paraview_plugin(). Compiling against ParaView 3.98 RC2, I get the<br>
following message:<br>
<br>
CMake Warning at<br>
/Users/quammen/dev/madai/build/MADAIWorkbench-ParaViewTracking-Debug/src/ParaView/CMake/ParaViewPlugins.cmake:1009<br>
(message):<br>
AUTOLOAD option is deprecated. Plugins built within ParaView source should<br>
use pv_plugin(..) macro with AUTOLOAD argument.<br>
<br>
This is a plugin built outside ParaView source, so should I use<br>
pv_plugin()? Is this change documented in a ParaView migration guide?<br>
<br>
Thanks,<br>
Cory<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></div><br></div>