[Paraview] ParaView 3.8-RC1 Not Copying Custom Plugins

Fri May 14 16:37:28 EDT 2010

I've never used PARAVIEW_EXTRA_EXTERNAL_MODULES before but what I have
figured out was to set it to PVMXADataModel and place your git repository
adjacent to my ParaView source directory. When I do this I get these
configure errors.

CMake Error at
C:/Kitware/ParaView/PVMXADataModel/PVMXADataModelParaViewImport.cmake:39
(INCLUDE):

 include could not find load file:

C:/Kitware/ParaView/PVMXADataModel/Resources/CMake/ParaViewPluginIncludeMXADataModel.cmake

Call Stack (most recent call first):

CMake/ParaViewCommon.cmake:678 (INCLUDE)

CMakeLists.txt:238 (INCLUDE)

 CMake Error at
C:/Kitware/ParaView/PVMXADataModel/PVMXADataModelParaViewImport.cmake:40
(INCLUDE):

include could not find load file:

C:/Kitware/ParaView/PVMXADataModel/Resources/CMake/LocateBoostSupportLibraries.cmake

Call Stack (most recent call first):

CMake/ParaViewCommon.cmake:678 (INCLUDE)

CMakeLists.txt:238 (INCLUDE)

I don't see these in the Repository. Are they missing from where I cloned
from?

On Fri, May 14, 2010 at 2:25 PM, Michael Jackson <
mike.jackson at bluequartz.net> wrote:

> 535:[mjackson at Shepard:Build]$ cmake ../
> -- The C compiler identification is GNU
> -- The CXX compiler identification is GNU
> -- Checking whether C compiler has -isysroot
> -- Checking whether C compiler has -isysroot - yes
> -- Checking whether C compiler supports OSX deployment target flag
> -- Checking whether C compiler supports OSX deployment target flag - yes
> -- Checking whether CXX compiler has -isysroot
> -- Checking whether CXX compiler has -isysroot - yes
> -- Checking whether CXX compiler supports OSX deployment target flag
> -- Checking whether CXX compiler supports OSX deployment target flag - yes
> -- Found Qt-Version 4.6.2 (using
> /Users/Shared/Toolkits/Qt-4.6.2-Cocoa/bin/qmake)
> -- Found Qt-Version 4.6.2 (using
> /Users/Shared/Toolkits/Qt-4.6.2-Cocoa/bin/qmake)
> -- [PVMXADataModel] Added the MXADataModel library.
> -- Plugin: AngReader enabled
> -- Plugin: CrystalInterfaceColoringFilter enabled
> -- Plugin: EDMFilter enabled
> -- Plugin: IPFFilter enabled
> -- Plugin: MXAReader enabled
> -- Plugin: H5DataIO enabled
> -- Plugin: Manta ray traced rendering disabled
> -- Plugin: Filters for Flux and Circulation Fields disabled
> -- Plugin: NetDMF file format reader disabled
> -- Plugin: Prism disabled
> -- Plugin: Point Sprites disabled
> -- Plugin: SierraPlotTools enabled
> -- Plugin: SLACTools disabled
> -- Plugin: VisItReaderPlugin disabled
> -- Plugin: Reader for *.h5part files disabled
> -- Plugin: Plugin for creating python coprocessing scripts disabled
> -- Plugin: Reader/Writer for Analyze and NIfTI. enabled
> -- Application: Standard ParaView Client enabled
> PARAVIEW_PLUGINLIST
> SierraPlotTools;AnalyzeReader;AnalyzeWriter;NIfTIReader;NIfTIWriter
> -- Application: Streaming ParaView Application disabled
> -- Application: Adaptive ParaView Application disabled
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /Users/Shared/Kitware-CVS/ParaView/Build
>
> I placed the message just inside the if (APPLE) statement. Maybe I am not
> writing my *ParaViewImport.cmake file correctly? That can be found at:
>
> git clone git://echo1.bluequartz.net/PVMXADataModel
>
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
>
> On May 14, 2010, at 1:40 PM, Dave Partyka wrote:
>
>  Hi Mike,
>>
>> Do you mind trying to print some messages then? When you call
>> ADD_PARAVIEW_PLUGIN the plugin gets Appended to PARAVIEW_PLUGINLIST and also
>> install rules should be created. Can you add this line say in
>> Applications\ParaView\CMakeLists.txt and then configure and see if you're
>> plugins get printed in the list of plugins?
>>
>> message("PARAVIEW_PLUGINLIST ${PARAVIEW_PLUGINLIST}")
>>
>> On Fri, May 14, 2010 at 11:02 AM, Michael Jackson <
>> mike.jackson at bluequartz.net> wrote:
>> This is still NOT working on the latest pull of the "release" branch of
>> ParaView. I can NOT simply do a "make install" on OS X and have my custom
>> plugins copied into the Application Bundle along with any other plugins that
>> are included with ParaView.
>> ___________________________________________________________
>>
>> Mike Jackson                      www.bluequartz.net
>>
>> On Apr 26, 2010, at 11:47 AM, Michael Jackson wrote:
>>
>> Thanks, I'll give that a try. "Make install" does fixup the bundle
>> correctly. I just left out my plugins.
>>
>> So I have to do a cpack run in order to get a working installation on my
>> local machine? ie, an "installation" that is NOT in my build directory?
>> Seems odd.
>>
>> --
>> Mike Jackson <www.bluequartz.net>
>>
>> On Apr 26, 2010, at 11:05 AM, Dave Partyka wrote:
>>
>> I would recommend:
>>
>> cpack --config <build-dir>/Applications/ParaView/CPackParaViewConfig.cmake
>> -G DragNDrop
>>
>> As per: http://paraview.org/Wiki/ParaView:Build_And_Install
>>
>> If you do make install I believe it just runs all install rules and I
>> don't believe any of the fixup bundle routines get called.
>>
>> On Mon, Apr 26, 2010 at 9:43 AM, Michael Jackson <
>> mike.jackson at bluequartz.net> wrote:
>> Just tried a 'Make install' and after installation (to the wrong
>> directory**) my custom plugins that are built as part of ParaView (using
>> PARAVIEW_EXTRA_EXTERNAL_MODULE). Is this going to be fixed before the full
>> release comes out?
>>
>>
>> **I have a CMAKE_INSTALL_PREFIX of /Users/Shared/Toolkits/ParaView-3.8 but
>> when I run 'make install' ParaView gets installed into /Applications? I
>> tried exporting DESTDIR=$CMAKE_INSTALL_PATH but that did not seem to help
>> either. I do not have write access to /Applications for this user account so
>> this "feature" is a real problem.
>>
>> ___________________________________________________________
>> 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/20100514/5f876703/attachment-0001.htm>