On 5/27/2015 11:37 PM, Peter Karasev wrote:
The workaround is to purge your PATH environment variable so that no
copies of cmake.exe are there.
It still feels like a bug
that could be fixed
; why should cmake 3.x allow old versions to interfere with it at runtime?
At a minimum, some kind of warning would make the issue more obvious
and save people some time.
I suspect this does not have anything to do with cmake being in the PATH
but rather cygwin being in the PATH. If you could send me the
CMakeError.log file that might show what is wrong. Also, the output
from the run.
-Bill
--
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/mailman/listinfo/cmake
