[Paraview] Add support for PARAVIEW_EXTRA_EXTERNAL_PLUGINS?

[Michael Jackson]

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 my EXTERNAL_MODULE? Currently most of my  
EXTERNAL_MODULES are compiled into the vtkPVFilters library, what is  
the difference between setting my Module as a  
PARAVIEW_EXTRA_EXTERNAL_MODULES vs PARAVIEW_EXTRA_EXTERNAL_PLUGINS?


---
Mike Jackson                 www.bluequartz.net



On Jan 14, 2009, at 10:41 AM, John Biddiscombe wrote:

>
>> 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).
>>
>
> And also to clarify. I did not intend to remove the  
> PARAVIEW_EXTRA_EXTERNAL_MODULES, only to add  
> PARAVIEW_EXTRA_EXTERNAL_PLUGINS
>
> JB