|
Notes |
|
|
(0025465)
|
|
David Partyka
|
|
2011-02-17 16:31
|
|
|
I now guard that particular install rule with a new QT_TESTING_INSTALL_DEVELOPMENT option. This option gets set to ON when PARAVIEW_INSTALL_DEVELOPMENT gets turned on. Also the file will now be installed in ${PV_INSTALL_CMAKE_DIR} (default being lib/paraview-<blah>/CMake) instead of just lib/cmake. |
|
|
|
(0025512)
|
|
Alan Scott
|
|
2011-02-18 20:27
|
|
|
|
|
(0032097)
|
|
Orion Poplawski
|
|
2013-12-30 22:34
|
|
This isn't working for us (Fedora) as of ParaView 4.1.0-RC2. We want to install paraview development files so users can develop against paraview using our paravew-devel package, so we need to set PARAVIEW_INSTALL_DEVELOPMENT_FILES=ON.
However, these files are getting installed in:
/usr/lib/CMake/QtTestingConfig.cmake
which in our case should probably be /usr/lib{,64}/paraview/cmake/. I may be able to tweak this, but if probably should be based on VTK_INSTALL_LIBRARY_DIR
Perhaps simply using a system qttesting (if possible) would be better though. |
|
|
|
(0037924)
|
|
Kitware Robot
|
|
2016-08-12 09:58
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page. |
|