That is not is ParaView anymore? When did it go away? I use it all the
time and recommend it to my first time users to compile their own
filters. I would vote to keep the functionality if it is not causing
problems for other parts of the build.
Why was it removed? Is it removed in CVS or
Michael
Read again carefully and this time look for the in fact it still
exists, but probably nobody uses it any more since plugins have improved
so much - I actually use it myself, so I'm playing deveils advocate,
but I like plugins better now...
JB
That is not is ParaView anymore? When
My point is that PARAVIEW_EXTRA_EXTERNAL_PLUGINS may be unnecessary and at
some point may be obsolete.
PARAVIEW_EXTRA_EXTERNAL_MODULES is useful when deploying ParaView with
extensions on a platform that does not support shared libraries (for
example Cray Xts and IBM Blue Genes).
-berk
On
Perhaps Tim's plugins should also have an option to compile in statically.
There is a lot of interest in running infovis capabilities on these platforms.
-Ken
On 1/14/09 8:31 AM, Berk Geveci berk.gev...@kitware.com wrote:
My point is that PARAVIEW_EXTRA_EXTERNAL_PLUGINS may be unnecessary
If we come up with a standard way of doing this, it would make my life
easier when I am building binaries so I am all for someone doing it
:-)
On Wed, Jan 14, 2009 at 10:39 AM, John Biddiscombe biddi...@cscs.ch wrote:
Perhaps Tim's plugins should also have an option to compile in statically.
I sooo missed the subtle difference between
PARAVIEW_EXTRA_EXTERNAL_MODULES and PARAVIEW_EXTRA_EXTERNAL_PLUGINS.
My eyes just saw what they wanted to see and the brain didn't process
it correctly.
So how does this mechanism work? Do I still need to have a
*ParaViewImport.cmake file in
Awesome. I have the same issues with keeping 2 CMake files for each
plugin. This eliminates that need and is less work for me. I vote keep
it/put it in.
Thanks for the excellent explanation.
_
Mike Jackson
