The "setenv" output will be gone (by default) as of CMake 2.8.7 because of this recent commit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5a94d099ddbd8f3d4b850957faa8c11f619c6f18 Does using ctest from 'next' or 'master' already show any improvement over 2.8.6? On Wed, Nov 16, 2011 at 4:14 PM, Bill Hoffman <bill.hoff...@kitware.com> wrote: > On 11/16/2011 4:11 PM, Sean McBride wrote: > >> >> The downside is that this solution would be fragile. xcodebuild's > > output is not guaranteed to be the same forever, it's not like a public > API. Already today, gcc and clang output pretty differently. I'm a > little worried this would bite us. >> >> Besides, improving regex performance would be a win everywhere, not > > just in this case. > > > > Still, we are already filtering the output some, and it is way too verbose > which is why it is the only place where this is a problem. It might be > worth exploring as a faster path to getting things working for you. > > -Bill > -- > > 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers > -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
