[Paraview] Proper Way to Include Plugins in ParaView 3.8 and beyond

[Dave Partyka]

Can do!

On Tue, Nov 30, 2010 at 9:44 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> I think I like the multiple PARAVIEW_EXTERNAL_PLUGINS_FILES idea. To
> avoid confusion for existing users of PARAVIEW_EXTERNAL_PLUGINS_FILE
> variable, we can keep the variable name same, just accept multiple
> values similar to PARAVIEW_EXTRA_EXTERNAL_MODULE. Dave, can you make
> that change?
>
> Utkarsh
>
> On Mon, Nov 29, 2010 at 6:03 PM, Michael Jackson
> <mike.jackson at bluequartz.net> wrote:
> > Lets try this again, from an even higher perspective:
> >
> > I have several git repositories. Each one holds a plugin project for
> > paraview. They are:
> >
> > PVMXA
> > PVDislocation
> > PVOIM
> >
> > The three projects are independent. Usually I would set
> > PARAVIEW_EXTRA_EXTERNAL_MODULE to "PVMXA;PVOIM;PVDislocation" and run
> CMake.
> > CMake would ask me for all the source directories for each "module" and
> > things went as planned. With the PARAVIEW_EXTERNAL_PLUGINS_FILE which one
> of
> > the repos would I store that in? (Rhetorical question..). I guess I can
> keep
> > the same file in _each_ of the repos with instructions telling the user
> how
> > to comment out what they don't need? Seems a bit odd to have to do it
> that
> > way. Now, if PARAVIEW_EXTERNAL_PLUGINS_FILE would actually be
> > PARAVIEW_EXTERNAL_PLUGINS_FILES (Note the plural) and I could assign
> > multiple files to it then this would be much better. Again, Having been
> out
> > of the ParaView plugin game for 9 months I may have missed something
> along
> > then way.
> >
> > Hopefully that is more clear in where I am getting confused.
> > --
> > Mike Jackson <www.bluequartz.net>
> >
> > On Nov 29, 2010, at 5:53 PM, Dave Partyka wrote:
> >
> >> In the file PARAVIEW_EXTERNAL_PLUGINS_FILE points to you can just
> >> enumerate all your plugins like so
> >>
> >> paraview_build_optional_plugin(Plugin1 "My Plugin 1" "/some/source/dir"
> >> ON)
> >> paraview_build_optional_plugin(Plugin2 "My Plugin 2"
> >> "/some/other/source/dir" ON)
> >>
> >> On Mon, Nov 29, 2010 at 5:27 PM, Michael Jackson
> >> <mike.jackson at bluequartz.net> wrote:
> >> I usually use PARAVIEW_EXTRA_EXTERNAL_MODULE to add my plugins. Is this
> >> the "proper" way now? In looking through the ParaView cmake files I
> found
> >> the PARAVIEW_EXTERNAL_PLUGINS_FILE variable which seems to only take a
> >> single value (a file path). What happens if I have multiple plugins in
> >> multiple project directories to add? Or is there another way that I
> should
> >> be upgrading all my plugins to use? Wiki entry that I missed?
> >>
> >> Thank
> >> ___________________________________________________________
> >> Mike Jackson                      www.bluequartz.net
> >> Principal Software Engineer       mike.jackson at bluequartz.net
> >> BlueQuartz Software               Dayton, Ohio
> >>
> >>
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20101130/fc12286f/attachment.htm>