[Paraview] ParaView 3.8-RC1 Not Copying Custom Plugins

[Michael Jackson]

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
>