Almost forgot about this.
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.
On Tue, Nov 30, 2010 at 9:55 AM, Dave Partyka wrote:
> Can do!
>
>
> On Tue, Nov 30, 2010 at 9:
Can do!
On Tue, Nov 30, 2010 at 9:44 AM, Utkarsh Ayachit <
utkarsh.ayac...@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
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
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
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, Micha
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 mul
