Almost forgot about this.<div><br></div><div>PARAVIEW_EXTRA_INSTALL_RULES_FILE now can be set to multiple semicolon separated files that will be looped over and included. Please let me know if you experience any issues.<br>
<br><div class="gmail_quote">On Tue, Nov 30, 2010 at 9:55 AM, Dave Partyka <span dir="ltr"><<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Can do!<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Tue, Nov 30, 2010 at 9:44 AM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think I like the multiple PARAVIEW_EXTERNAL_PLUGINS_FILES idea. To<br>
avoid confusion for existing users of PARAVIEW_EXTERNAL_PLUGINS_FILE<br>
variable, we can keep the variable name same, just accept multiple<br>
values similar to PARAVIEW_EXTRA_EXTERNAL_MODULE. Dave, can you make<br>
that change?<br>
<br>
Utkarsh<br>
<br>
On Mon, Nov 29, 2010 at 6:03 PM, Michael Jackson<br>
<div><div></div><div><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
> Lets try this again, from an even higher perspective:<br>
><br>
> I have several git repositories. Each one holds a plugin project for<br>
> paraview. They are:<br>
><br>
> PVMXA<br>
> PVDislocation<br>
> PVOIM<br>
><br>
> The three projects are independent. Usually I would set<br>
> PARAVIEW_EXTRA_EXTERNAL_MODULE to "PVMXA;PVOIM;PVDislocation" and run CMake.<br>
> CMake would ask me for all the source directories for each "module" and<br>
> things went as planned. With the PARAVIEW_EXTERNAL_PLUGINS_FILE which one of<br>
> the repos would I store that in? (Rhetorical question..). I guess I can keep<br>
> the same file in _each_ of the repos with instructions telling the user how<br>
> to comment out what they don't need? Seems a bit odd to have to do it that<br>
> way. Now, if PARAVIEW_EXTERNAL_PLUGINS_FILE would actually be<br>
> PARAVIEW_EXTERNAL_PLUGINS_FILES (Note the plural) and I could assign<br>
> multiple files to it then this would be much better. Again, Having been out<br>
> of the ParaView plugin game for 9 months I may have missed something along<br>
> then way.<br>
><br>
> Hopefully that is more clear in where I am getting confused.<br>
> --<br>
> Mike Jackson <<a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a>><br>
><br>
> On Nov 29, 2010, at 5:53 PM, Dave Partyka wrote:<br>
><br>
>> In the file PARAVIEW_EXTERNAL_PLUGINS_FILE points to you can just<br>
>> enumerate all your plugins like so<br>
>><br>
>> paraview_build_optional_plugin(Plugin1 "My Plugin 1" "/some/source/dir"<br>
>> ON)<br>
>> paraview_build_optional_plugin(Plugin2 "My Plugin 2"<br>
>> "/some/other/source/dir" ON)<br>
>><br>
>> On Mon, Nov 29, 2010 at 5:27 PM, Michael Jackson<br>
>> <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>> I usually use PARAVIEW_EXTRA_EXTERNAL_MODULE to add my plugins. Is this<br>
>> the "proper" way now? In looking through the ParaView cmake files I found<br>
>> the PARAVIEW_EXTERNAL_PLUGINS_FILE variable which seems to only take a<br>
>> single value (a file path). What happens if I have multiple plugins in<br>
>> multiple project directories to add? Or is there another way that I should<br>
>> be upgrading all my plugins to use? Wiki entry that I missed?<br>
>><br>
>> Thank<br>
>> ___________________________________________________________<br>
>> Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> BlueQuartz Software Dayton, Ohio<br>
>><br>
>><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br></div>