Tyler Roscoe wrote: > On Fri, Apr 30, 2010 at 12:03:12PM -0400, Brad King wrote: >> Unfortunately this can't be fixed upstream without breaking the >> legacy extension-finding feature. > > Isn't this what CMake policies are for? Or is the offending code buried > in some dark corner where policies won't help?
Yes, a policy would work for this, but it would trigger *many* warnings for *many* projects. We've learned to introduce them only when absolutely necessary. -Brad _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
