[Paraview] Redistributable ParaView OS X Package is unusable.

Tue May 24 17:42:28 EDT 2011

Bad ParaView preferences in the ~/.config/ParaView directory. Blew it away and started ParaView just fine. I have had problems with ParaView preferences in the past.

 Thanks for the help.
--
Mike Jackson <www.bluequartz.net>

On May 24, 2011, at 8:14 AM, David Partyka wrote:

> Qt 4.6.3 built by hand with cocoa, the binary is x64 only targeting 10.5. I am building from the tip of the 'release' branch.
> 
> Qt Configure command:
> 
> export QMAKE_MACOSX_DEPLOYMENT_TARGET=10.5
> ./configure --prefix=/Users/partyd/Dashboards/Support/qt-4.6.3-MacOSX10.5/bin -nomake demos -nomake examples -arch x86_64 -opensource -release -cocoa -shared
> 
> 
> I also pass these in as -D arguments on initial configure with cmake.
> 
> set(CMAKE_OSX_ARCHITECTURES "x86_64" CACHE STRING "force build for 64-bit Leopard" FORCE)
> set(CMAKE_OSX_DEPLOYMENT_TARGET "10.5" CACHE STRING "force build for 64-bit Leopard" FORCE)
> set(CMAKE_OSX_SYSROOT "/Developer/SDKs/MacOSX10.5.sdk" CACHE PATH "force build for 64-bit Leopard" FORCE)
> 
> On Mon, May 23, 2011 at 10:30 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> Dave,
>  What is the configuration you are using? Qt Version? As Carbon or Cocoa? Universal Binaries or x64 only? Self build or download from Nokia?
> 
>  What tag from paraview git repository are you using? I may be able to get my environment going like yours.
> 
>  I also tried the latest ParaView master from head and my plugins need to be updated for that to work so using that is out of the question at this point.
> 
>  This is what I have tried and have not worked:
>    Qt 4.6.2 Self built with NO custom plugins
>    Qt 4.7.2 Self built with NO custom plugins
>    "make install" of both of the above.
>    using sudo for everything to avoid possible permissions issues.
> 
> I'll download the prebuilt Qt libraries from Nokia and try those. I guess I could also try CMake 2.8.4
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
> Principal Software Engineer       mike.jackson at bluequartz.net
> BlueQuartz Software               Dayton, Ohio
> 
> 
> 
> On May 23, 2011, at 6:33 PM, David Partyka wrote:
> 
> > Can you provide the initial cmake configuration details of your vanila paraview build?
> >
> > On Mon, May 23, 2011 at 6:02 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> > I tried this also:
> >
> > 562:[mjackson at ferb2:4.6.2]$ sudo rm -rf _CPack_Packages/; sudo cpack -G ZIP --config Applications/ParaView/CPackParaViewConfig.cmake
> > CPack: Create package using ZIP
> > CPack: Install projects
> > CPack: - Run preinstall target for: ParaView Runtime Libs
> > CPack: - Install project: ParaView Runtime Libs
> > CPack: - Run preinstall target for: HDF5 Core Library
> > CPack: - Install project: HDF5 Core Library
> > CPack: - Run preinstall target for: VTK Runtime Libs
> > CPack: - Install project: VTK Runtime Libs
> > CPack: - Run preinstall target for: ParaView Components
> > CPack: - Install project: ParaView Components
> > CPack: Create package
> > CPack Error: Problem while adding file< /Users/Shared/OpenSource/ParaView-3.10.1/4.6.2/_CPack_Packages/Darwin-i386/ZIP/ParaView-3.10.1-Darwin-i386/lib/paraview-3.10/libCosmo.dylib> to archive </Users/Shared/OpenSource/ParaView-3.10.1/4.6.2/_CPack_Packages/Darwin-i386/ZIP/ParaView-3.10.1-Darwin-i386.zip> .ERROR =archive_write_header: Filetype not supported
> > CPack Error: Problem compressing the directory
> > CPack Error: Error when generating package: ParaView
> >
> >
> > And that was built against Qt 4.6.2.
> > ___________________________________________________________
> > Mike Jackson                      www.bluequartz.net
> > Principal Software Engineer       mike.jackson at bluequartz.net
> > BlueQuartz Software               Dayton, Ohio
> >
> > On May 23, 2011, at 5:56 PM, David Partyka wrote:
> >
> > > I am really unsure, I haven't ever seen these kinds of errors before and I am unable to reproduce this. sla.r on my system appears to just contain license information. Have you tried manually removeing the _CPack_Packages directory in your build tree to see if for some reason cpack isn't able to blow it away entirely?
> > >
> > > On Mon, May 23, 2011 at 5:24 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> > > When running CPack on a "clean" paraview build directory where NONE of my plugins are being build I get the following after trying to run CPack:
> > >
> > > cpack -G DragNDrop --config Applications/ParaView/CPackParaViewConfig.cmake
> > > .....
> > >
> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r:522: ### /usr/bin/Rez - String spans lines.
> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r: ### /usr/bin/Rez - Since errors occurred, /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/temp-udco.dmg's resource fork was not completely updated.
> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r: ### /usr/bin/Rez - SysError -37 during set file info.
> > >
> > > CPack Error: Problem compressing the directory
> > > CPack Error: Error when generating package: ParaView
> > >
> > >
> > >
> > > ___________________________________________________________
> > > Mike Jackson                      www.bluequartz.net
> > > Principal Software Engineer       mike.jackson at bluequartz.net
> > > BlueQuartz Software               Dayton, Ohio
> > >
> > > On May 23, 2011, at 4:32 PM, David Partyka wrote:
> > >
> > > > I've never seen anything like that, as that is the same process I used to make the 3.10.1 binaries. Though I did use cmake 2.8.4. Are you using a really new Qt or something along those lines?
> > > >
> > > > On Mon, May 23, 2011 at 4:19 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> > > > I followed the directions on the wiki page to compile my own ParaView 3.10.1 because I have some custom plugins that I compile. The .dmg image was created just fine but the contained "ParaView.app" when launched only has a menu bar that has "New Application" menu. Nothing else. Yet when I run it from the Build folder everything works just fine. Is there something in the cmake configuration of ParaView that I need to set that tells CMake that I am going to making a redistributable package? The same thing happens if I try a "make install" from the command line. This is on OS X 10.6.8 with CMake 2.8.3 and the ParaView 3.10.1 sources from the web site.
> > > > ___________________________________________________________
> > > > 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
> > > >
> > >
> > >
> >
> >
> 
> 