This topic itself looks simple enough, and it fixes the problem you've
observed. I guess my question is, are there still other instances of
this problem, and why wouldn't we want to do this for inputs *not*
specified by full path? Shouldn't we infer the correct full path at
add_custom_command time if it's not specified by full path? And
shouldn't that too be normalized?
D
--
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
