Sorry, but no, not for 2.8.6. From now on we will only consider fixes for regressions, and we hope to finalize 2.8.6 by end of next week.<br><br>On the other hand, you can override all the settings in CTestConfig already, if you set the variables at the right point in a ctest -S script (typically after the call to ctest_configure...)<br>
<br>That would be an alternative you can consider for using with any ctest 2.8.x<br><br>If you really want a change like this in CMake, we'd consider it for the next release, but it should be in 'next' and tested on the dashboard well before the release candidate phase leading up to a release.<br>
<br>Thx,<br>David C.<br><br><br>On Thursday, September 22, 2011, Jean-Christophe Fillion-Robin <<a href="mailto:jchris.fillionr@kitware.com">jchris.fillionr@kitware.com</a>> wrote:<br>> Hi Dave,<br>><br>> Would it be possible to include the following topic in the release:<br>
> <a href="https://github.com/jcfr/CMake/tree/check-ctestconfig-in-builddir">https://github.com/jcfr/CMake/tree/check-ctestconfig-in-builddir</a><br>><br>> The change is documented and tests have been added:<br>
><br>> Expect CTestConfig.cmake in either the build or source directory <<a href="https://github.com/jcfr/CMake/commit/268c0e5d015e36145c4d48c91d169c636ea172cd">https://github.com/jcfr/CMake/commit/268c0e5d015e36145c4d48c91d169c636ea172cd</a>> …<br>
><br>> Provide the ability to configure CTest with setting different from the one<br>> available in the source tree by checking first if CTestConfig.cmake<br>> exists in the build tree first.<br>><br>><br>
><br>> The motivation is to allow build system checking out external project to<br>> test and/or package them and submit the associated results to a different<br>> dashboard than the one specified (or not) in the source of the external<br>
><br>><br>> project.<br>><br>> For example, the build system of Slicer can checkout, build, test<br>> and package what I will call "extension". These extensions can be developed<br>> by third party who can test and submit to their own dashboard / project.<br>
><br>><br>> When checkout by Slicer build system, the default dashboard can be now<br>> overwritten by adding a custom CTestConfig.cmake to the build directory.<br>> And if not overwritten, it would avoid to create CTestConfig.cmake within<br>
><br>><br>> the source checkout of the extension.<br>><br>> Thanks<br>> Jc<br>><br>> On Thu, Sep 22, 2011 at 4:14 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
>><br>>> The CMake 2.8.6 release candidate stream continues! You can find the<br>>> source and binaries here:<br>>><br>>> <a href="http://www.cmake.org/files/v2.8/?C=M;O=D">http://www.cmake.org/files/v2.8/?C=M;O=D</a><br>
>><br>>> This email is also available on the Kitware blog at<br>>><br>>> <a href="http://www.kitware.com/blog/home/post/170">http://www.kitware.com/blog/home/post/170</a><br>>><br>>> This is the last rc before the final release, unless somebody finds a<br>
>> showstopper issue between now and next Thursday.<br>>><br>>> This release candidate we do not have pre-built binaries for the<br>>> SunOS anymore. As mentioned on the CMake mailing list recently, our<br>
>> Sun hardware has bitten the proverbial dust.<br>>><br>>> However, we are now providing two sets of installers for the Mac.<br>>> The "Darwin" versions are for Mac OSX 10.4 and later, and are "ppc;i386"<br>
>> universal binaries. The "Darwin64" versions are for 10.6 and later,<br>>> and are "x86_64;i386" universal binaries.<br>>><br>>> Following is the list of changes in this release. Since we switched to<br>
>> git, this list is now the 'git log' one line summary written by the<br>>> named CMake developers.<br>>><br>>> Please try this version of CMake on your projects and report any<br>>> issues to the list or the bug tracker.<br>
>><br>>> Happy building!<br>>> -Dave<br>>><br>>><br>>> Changes in CMake 2.8.6-rc4 (since 2.8.6-rc3)<br>>> --------------------------------------------<br>>> Alex Neundorf (3):<br>
>> FindFLEX.cmake: also search the include dir<br>>> Fix typos in FeatureSummary.cmake (#12462)<br>>> Don't warn when setting a property multiple times to the same value #12464<br>>><br>
>> Bill Hoffman (2):<br>>> For VS Intel Fortran IDE builds, add a check to find the Fortran<br>>> library PATH.<br>>> Enable Fortran tests for IDE builds.<br>>><br>>> Brad King (5):<br>
>> FortranCInterface: Compile separate Fortran lib in VerifyC[XX]<br>>> Move IntelVSImplicitPath project to better location<br>>> Simplify IntelVSImplicitPath detection project<br>>> libarchive: Fix ssize_t detection with mingwrt 3.20<br>
>> Make file(DOWNLOAD) fail on http error<br>>><br>>> David Cole (8):<br>>> Tests: Add a KWStyle test, equivalent to the make StyleCheck target<br>>> KWStyle Test: Activate by default if KWStyle is found<br>
>> Xcode: Use EFFECTIVE_PLATFORM_NAME reference in ComputeOutputDir<br>>> Xcode: Add test to demonstrate iOS project in Xcode<br>>> CMake: Reference test targets only when BUILD_TESTING is ON<br>
>> Tests: Add the more modern Mac64 nightly build<br>>> Release Scripts: Use Qt 4.7.4 on dashmacmini5 (#12460)<br>>> Revert "FindThreads: Try pthreads with no special option first (#11333)"<br>
>><br>>> Eric NOULARD (4):<br>>> CPack fix #12449 doc mispelled<br>>> CPack fix template too<br>>> CPackDeb fix #10325 automagically use fakeroot for DEB if<br>>> fakeroot is found<br>
>> CPackRPM authorize per-component pre/post-[un]install scripts (#0012063)<br>>><br>>> Marcus D. Hanwell (4):<br>>> Just code style changes.<br>>> Don't warn when nothing to do in visibility function.<br>
>> Made ADD_COMPILER_EXPORT_FLAGS into a macro.<br>>> Make add_compiler_export_flags a function again.<br>>><br>>> Rolf Eike Beer (1):<br>>> remove stray brace in CPackDeb documentation<br>
>> --<br>>><br>>> Powered by <a href="http://www.kitware.com">www.kitware.com</a><br>>><br>>> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>>> Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a><br>>><br>>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a> <<a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a>><br>
><br>><br>><br>> --<br>> +1 919 869 8849 <tel:%2B1%20919%20869%208849><br>><br>>