Updated the paraview and paraview-mpi packaging to build the new 3.0.2 version that is uses qt4-x11 for its user interface. Fixed the BuildDependsOnly fink validation error in both packages.
Removed prefix portion of path for VTK_INSTALL_QT_DIR environmental to
prevent doubling of prefix. Packages pass fink validate.
File Added: paraview-mpi.info
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
fink fetch paraview
Information about 7357 packages read in 3 seconds.
curl --connect-timeout 30 -f -L -A 'fink/0.27.4' -O http://www.paraview.org/files/v3.0/ParaView-3.0.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
### execution of curl failed, exit code 22
Downloading the file "ParaView-3.0.2.tar.gz" failed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 3.0.x releases of ParaView are not provided as tarballs. They are only available from upstream as cvs pull's of the specified release branch. Please follow the instructions in theDescPackaging section of paraview.info and paraview-mpi.info files. The required steps are...
When this package goes into fink 10.4 unstable, we will have to add the tarball created from the cvs pull of the release branch to the local fink file repository (like we currently do for pymol-py).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK--now that a source tarball is generated, they fail on a clean build in the configuration phase due to the lack of an environment variable:
-- Application: default ParaView Client enabled
-- Application: Custom Server enabled
-- Application: DobranoViz enabled
CMake Error: This project requires some variables to be set,
and cmake can not find them.
Please set the following variables:
QT_PNG_LIBRARY (ADVANCED)
It appears to by trying to install files directly into the filesystem rather than the .deb:
...
-- Installing /sw/src/fink.build/root-paraview-3.0.2-1000/sw/bin/paraview
-- Installing /sw/lib/paraview-3.0/libQtCore.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtGui.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtNetwork.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtXml.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtTest.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtAssistantClient.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Install configuration: ""
-- Installing /sw/src/fink.build/root-paraview-3.0.2-1000/sw/bin/pvTestDriver
...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any advice on fixing this would be appreciated. Without passing a value for "-DVTK_INSTALL_QT_DIR" the plugins get installed in a non-standard place for fink (/sw/plugins/designer) but are in fact installed in the build directories as expected. My previous attempts to use...
-DVTK_INSTALL_QT_DIR:STRING=%p/lib/%n-3.0 \
resulted in doubled paths for installation "/sw/sw/lib/paraview-3.0. I'll try moving that flag down later in the list of passed CMAKE flags to see if that helps but I'm not too optimistic.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added @FINKDESTDIR@ to ParaView-3.0.1/VTK/GUISupport/CMakeLists.txt and adopted use of patchscript so that the tar method used for installing paraview's QT libs places them in the destination directory for packaging.
File Added: paraview.info
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for not responding earlier; I am just now trying to catch up on this.
I haven't yet understood all of the new installation philosophy.
For example:
> Added @FINKDESTDIR@ to ParaView-3.0.1/VTK/GUISupport/CMakeLists.txt and
> adopted use of patchscript so that the tar method used for installing
> paraview's QT libs places them in the destination directory for packaging.
Are these the libQtCore.dylib etc that are copied from /sw/lib/qt4-x11/lib?
I don't understnad what is the idea of copying them at all, unless one wants to make a stand-alone app package independent of Fink.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Martin,
You've hit the nail on the head. The entire patch for paraview(-mpi) works around issues resulting from the fact that Paraview 3.0.x expects to be normally built as an application on Mac OS X. The first section replaces the IF(APPLE) conditionals with IF(Q_WS_MAC) so that we can build Paraview 3.0.2 against a non-Carbon (ie X11-based) Qt 4.0 package. The last part I just added works around the fact that (for the QT related shared libraries only) tar is being used for the installation method. I've passed this upstream as a bug report for fixing in 3.0.3. I believe the current packaging should be fine now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview.patch
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview-mpi.info
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview.info
Logged In: YES
user_id=403009
Originator: YES
Removed prefix portion of path for VTK_INSTALL_QT_DIR environmental to
prevent doubling of prefix. Packages pass fink validate.
File Added: paraview-mpi.info
Logged In: YES
user_id=353035
Originator: NO
The download URL isn't working:
fink fetch paraview
Information about 7357 packages read in 3 seconds.
curl --connect-timeout 30 -f -L -A 'fink/0.27.4' -O http://www.paraview.org/files/v3.0/ParaView-3.0.2.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
### execution of curl failed, exit code 22
Downloading the file "ParaView-3.0.2.tar.gz" failed.
Logged In: YES
user_id=403009
Originator: YES
The 3.0.x releases of ParaView are not provided as tarballs. They are only available from upstream as cvs pull's of the specified release branch. Please follow the instructions in theDescPackaging section of paraview.info and paraview-mpi.info files. The required steps are...
cvs -d :pserver:anoncvs@www.paraview.org:/cvsroot/ParaView3 login
cvs -d :pserver:anoncvs@www.paraview.org:/cvsroot/ParaView3 checkout -r ParaView-3-0-2 ParaView3
mv ParaView3 ParaView-3.0.2
tar --exclude=CVS -zcvf ParaView-3.0.2.tar.gz ParaView-3.0.2
When this package goes into fink 10.4 unstable, we will have to add the tarball created from the cvs pull of the release branch to the local fink file repository (like we currently do for pymol-py).
Logged In: YES
user_id=353035
Originator: NO
OK--now that a source tarball is generated, they fail on a clean build in the configuration phase due to the lack of an environment variable:
-- Application: default ParaView Client enabled
-- Application: Custom Server enabled
-- Application: DobranoViz enabled
CMake Error: This project requires some variables to be set,
and cmake can not find them.
Please set the following variables:
QT_PNG_LIBRARY (ADVANCED)
-- Configuring done
### execution of /var/tmp/tmp.0.s8wEe7 failed, exit code 255
Logged In: YES
user_id=403009
Originator: YES
Add Depends on libpng3-shlibs and BuildDepends on libpng3 to paraview.info and paraview-mpi.info.
File Added: paraview.info
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview-mpi.info
Logged In: YES
user_id=353035
Originator: NO
It appears to by trying to install files directly into the filesystem rather than the .deb:
...
-- Installing /sw/src/fink.build/root-paraview-3.0.2-1000/sw/bin/paraview
-- Installing /sw/lib/paraview-3.0/libQtCore.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtGui.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtNetwork.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtXml.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtTest.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Installing /sw/lib/paraview-3.0/libQtAssistantClient.dylib
tar: /sw/lib/paraview-3.0: Cannot chdir: No such file or directory
tar: Error is not recoverable: exiting now
-- Install configuration: ""
-- Installing /sw/src/fink.build/root-paraview-3.0.2-1000/sw/bin/pvTestDriver
...
Logged In: YES
user_id=403009
Originator: YES
Any advice on fixing this would be appreciated. Without passing a value for "-DVTK_INSTALL_QT_DIR" the plugins get installed in a non-standard place for fink (/sw/plugins/designer) but are in fact installed in the build directories as expected. My previous attempts to use...
-DVTK_INSTALL_QT_DIR:STRING=%p/lib/%n-3.0 \
resulted in doubled paths for installation "/sw/sw/lib/paraview-3.0. I'll try moving that flag down later in the list of passed CMAKE flags to see if that helps but I'm not too optimistic.
Logged In: YES
user_id=403009
Originator: YES
Added @FINKDESTDIR@ to ParaView-3.0.1/VTK/GUISupport/CMakeLists.txt and adopted use of patchscript so that the tar method used for installing paraview's QT libs places them in the destination directory for packaging.
File Added: paraview.info
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview.patch
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview-mpi.info
Logged In: YES
user_id=403009
Originator: YES
Make sure QT designer plugins go in their own subdirectory.
File Added: paraview.info
Logged In: YES
user_id=403009
Originator: YES
File Added: paraview-mpi.info
Logged In: YES
user_id=60552
Originator: NO
Sorry for not responding earlier; I am just now trying to catch up on this.
I haven't yet understood all of the new installation philosophy.
For example:
> Added @FINKDESTDIR@ to ParaView-3.0.1/VTK/GUISupport/CMakeLists.txt and
> adopted use of patchscript so that the tar method used for installing
> paraview's QT libs places them in the destination directory for packaging.
Are these the libQtCore.dylib etc that are copied from /sw/lib/qt4-x11/lib?
I don't understnad what is the idea of copying them at all, unless one wants to make a stand-alone app package independent of Fink.
Logged In: YES
user_id=403009
Originator: YES
Martin,
You've hit the nail on the head. The entire patch for paraview(-mpi) works around issues resulting from the fact that Paraview 3.0.x expects to be normally built as an application on Mac OS X. The first section replaces the IF(APPLE) conditionals with IF(Q_WS_MAC) so that we can build Paraview 3.0.2 against a non-Carbon (ie X11-based) Qt 4.0 package. The last part I just added works around the fact that (for the QT related shared libraries only) tar is being used for the installation method. I've passed this upstream as a bug report for fixing in 3.0.3. I believe the current packaging should be fine now.