Cory,<div><br></div><div>On Thu, Nov 15, 2012 at 3:25 PM, 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
By the way, it seems strange to have to use both a CMakeLists.txt file<br>and plugin.cmake to define a plugin. It would be nice if everything<br>could go in one or the other.<br></blockquote><div> </div></div><div>The separation of plugin.cmake and CMakeLists.txt is similar to what's done for VTK modules. It makes it possible for ParaView to automatically locate plugins contained in directories without having to update the top-level CmakeLists.txt file. </div>
<div><br></div><div>Utkarsh<br><div class="gmail_extra"><br></div></div>