On 10/25/2013 4:36 PM, James Bigler wrote:
My experience mirrored Clint's. Our version of CMake on the farm was at
2.8.12, but locally developers were at differing versions. What made
matters worse is that it is a lot harder to diagnose problems from farm
built binaries, so it wasn't until one of the 4 developers looking into
this problem was able to get a local debug build were we able to figure
out it was a stack problem. At that point, I happened to remember that
CMake modified the default stack size, and with a bit of investigation
realized the flag was missing on newer versions. Basically I wasn't
expecting CMake versions to be a contributing factor, so it was one of
the last things I looked at.
Well, I guess it is too late to do this in a different way now. :)
Any suggestions on how/where a warning could be placed to help people
out with this?
-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://www.cmake.org/mailman/listinfo/cmake
