This is a continuation of the object file generation issues that
FindCuda was seeing with CMake master.
The issue for FindCuda was in regards to directory paths being
normalized, which was added in commit 4959f3413c, but the issue is
actually more widespread with add_custom_command not collapsing any
OUTPUT or DEPENDS paths. This means that if add_custom_command outputs
the path "${CMAKE_CURRENT_BINARY_DIR}//./foo.h" and another custom
command DEPENDS on
"${CMAKE_CURRENT_BINARY_DIR}/foo.h" we fail to realize that these two
paths are the same and connect the two custom commands properly.
I have pushed a branch called normalize_custom_command_paths to stage
and I am interested in peoples feedback on how I solved this issue.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
