On Fri, 2015-03-06 at 17:34 -0600, Michael Catanzaro wrote: > This is a heads-up in case this issue is still present when CMake 3.2 > is > released It looks like the CMake developers identified the cause of the issue and will have it fixed before 3.2 is released. Michael