Notes |
|
(0034148)
|
Orion Poplawski
|
2015-02-03 18:00
|
|
This appears to be fixed in VTK git and can probably be closed. |
|
|
(0034150)
|
Orion Poplawski
|
2015-02-03 18:33
|
|
Sorry, my mistake, this is still an issue:
CMake/vtkModuleTop.cmake:
# Generate VTKConfig.cmake for the install tree.
set(VTK_CONFIG_CODE "
# Compute the installation prefix from this VTKConfig.cmake file location.
get_filename_component(VTK_INSTALL_PREFIX \"\${CMAKE_CURRENT_LIST_FILE}\" PATH)")
# Construct the proper number of get_filename_component(... PATH)
# calls to compute the installation prefix.
string(REGEX REPLACE "/" ";" _count "${VTK_INSTALL_PACKAGE_DIR}")
foreach(p ${_count})
set(VTK_CONFIG_CODE "${VTK_CONFIG_CODE}
get_filename_component(VTK_INSTALL_PREFIX \"\${VTK_INSTALL_PREFIX}\" PATH)")
endforeach() |
|
|
(0034163)
|
Dave DeMarle
|
2015-02-05 12:13
|
|
@Ben, please take a look and see if this is as trivial to fix as it looks and decide on 6.2 or 6.3 target. |
|
|
(0034198)
|
Ben Boeckel (Kitware)
|
2015-02-09 15:54
|
|
|
|
(0034207)
|
Brad King
|
2015-02-11 10:41
|
|
|
|
(0034210)
|
Ben Boeckel (Kitware)
|
2015-02-11 14:18
|
|
|