[CMake] Ctest not configuring properly due to DartConfiguration.tcl ?

David Cole david.cole at kitware.com
Mon Aug 30 09:22:44 EDT 2010


Not sure about this one.

Can you share your project source tree / CMakeLists files?

Is it publicly available?

Or reproduce the problem with a very small representative CMakeLists file?


Thanks,
David


On Mon, Aug 30, 2010 at 8:41 AM, Johny <Johny.Jose at cern.ch> wrote:

>  I did what you said but now I have a different problem. I see this command
> being run and it has its output as G__CDB.cxx
>
> "/home/johny/opt/cmake/bin/ctest" --launch --target-name CDB --build-dir
> /home/johny/opt/alice/AliRootInstall/STEER --output G__CDB.cxx
>
> however this file is not created in that directory. The file is generated
> through a custom command. How do i fix this ?
>
> Cheers,
> Johny
>
>
> On 08/30/2010 01:51 PM, David Cole wrote:
>
> If you are going to run a dashboard with "ctest -D Experimental" then the
> CTEST_USE_LAUNCHERS setting has to be saved in the CMake cache so that
> *cmake*, at configure time, knows how to generate the proper command lines
> in the generated Makefiles.
>
> So you need to pass -DCTEST_USE_LAUNCHERS=ON to cmake at configure time.
>
>  The other variables may be set in a CTestCustom.cmake file at the top
> level of your build tree.
>
>  There is also a setting in CDash that tells it whether or not to display
> labels on a per-project basis: on the "edit project" page, on the
> "Miscellaneous" tab, there's a "Display Labels" checkbox. Make sure that's
> checked in your CDash project settings.
>
>
>  HTH,
> David
>
>
> On Mon, Aug 30, 2010 at 7:38 AM, Johny <Johny.Jose at cern.ch> wrote:
>
>>  Well i wasn't able to see labels on my builds, and then later i cudn't
>> see build reports either. I was messing around with the configuration files
>> and i guess i must have put something in the wrong place.
>>
>> So basically in which file do i have to set the variables
>> CTEST_CUSTOM_MAXIMUM_NUMBER_OF_ERRORS,
>> CTEST_CUSTOM_MAXIMUM_NUMBER_OF_WARNINGS,
>> CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE , CTEST_USE_LAUNCHERS  so that
>> when i run ctest -D Experimental those values will be used and my build
>> results get labeled ?
>>
>> Cheers,
>> Johny
>>
>>
>>
>>
>> On 08/30/2010 01:35 PM, David Cole wrote:
>>
>> You're not doing anything wrong. DartConfiguration.tcl is simple a legacy
>> file name that is still in use. It is actually: not tcl, does not require
>> Dart usage...
>>
>>  Is there a problem with your submissions to your CDash server? Do you
>> get some kind of error?
>>
>>
>> On Mon, Aug 30, 2010 at 7:22 AM, Johny <Johny.Jose at cern.ch> wrote:
>>
>>> Hey,
>>>
>>> I was trying to use the ctest custom configuration file CTestCustom.ctest
>>> to set my limits for warnings and errors higher than the defaults and also
>>> to enable labels while building using the CTEST_USE_LAUNCHERS variable. I
>>> have set all this up in the file however when i run Ctest -D Experimental i
>>> get this message :
>>>
>>> UpdateCTestConfiguration  from :*
>>> /home/johny/opt/alice/AliRootInstall/DartConfiguration.tcl*
>>> Parse Config file:*
>>> /home/johny/opt/alice/AliRootInstall/DartConfiguration.tcl*
>>>
>>> Is this supposed to happen? Where is this DartConfiguration.tcl file
>>> coming from ? I'm using CDash not DART. I even tried specify the
>>> configuration file to use by ctest using the option --ctest-config but it
>>> still gives me this message. What am i doing wrong ?
>>>
>>> Cheers,
>>> Johny
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100830/fe3723df/attachment-0001.htm>


More information about the CMake mailing list