IN itk this is what we typically do in ctest scripts.
After
CTEST_CONFIGURE (BUILD "${CTEST_BINARY_DIRECTORY}")
place
CTEST_READ_CUSTOM_FILES("${CTEST_BINARY_DIRECTORY}")
On Fri, Nov 13, 2009 at 3:49 PM, Alexander Neundorf
<a.neundorf-w...@gmx.net> wrote:
> On Wednesday 11 November 2009, Maik Beckmann wrote:
>> Ok, it works like this:
>>
>> cmCTest::ReadCustomConfigurationFileTree searches for
>> CTestCustom.(cmake|ctest) and reads it. If found, this code the inte
>> same method
>> if ( found )
>> {
>> cmCTest::t_TestingHandlers::iterator it;
>> for ( it = this->TestingHandlers.begin();
>> it != this->TestingHandlers.end(); ++ it )
>> {
>> cmCTestLog(this, DEBUG,
>> "* Read custom CTest configuration vectors for handler: "
>> << it->first.c_str() << " (" << it->second << ")" << std::endl);
>> it->second->PopulateCustomVectors(mf);
>> }
>> }
>> gives the handlers, among them the test handler, the chance to pull
>> what was found in CTestCustom.
>>
>> But when the handler is called, it clears the content of
>> CustomTestsIgnore and tried to populate it from the current cmMakefile
>> instance, which never read neither even looked for CTestCustom.
>>
>> Meh!
>
> I'm also usually confused at which point ctest reads which files and which
> variables make it through...
>
> Alex
> _______________________________________________
> 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
>
_______________________________________________
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
