Would it be possible to use ctest -D without actually submitting to CDash? Something like<br><br>ctest -D ExperimentalCoverage<br><br>seems like it would do the same thing that nightlies do, just for a single local build without submitting the results.<br>
<br>Ceej<br>aka Chris Hillery<br><br><div class="gmail_quote">On Mon, Jun 7, 2010 at 6:36 PM, Clark Gaebel <span dir="ltr"><<a href="http://cg.wowus.cg">cg.wowus.cg</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This is almost perfect for my needs with a bit of trivial tweaking. I<br>
wish support was built-in to cmake just like valgrind-on-nightly-test<br>
was. Oh well.<br>
<br>
Thank you so much,<br>
-Clark<br>
<div><div></div><div class="h5"><br>
On 06/07/10 17:46, Ben Boeckel wrote:<br>
> Clark Gaebel <<a href="http://cg.wowus.cg" target="_blank">cg.wowus.cg</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>> wrote:<br>
><br>
>> Hello,<br>
>><br>
>> I've currently set up CMake and CTest for my building and testing needs,<br>
>> but CDash just isn't for me. How do I set up CTest to run all the tests<br>
>> in Valgrind? Again, I don't want to use CDash - just CTest.<br>
>><br>
>> Also, it'd be great if I get output on leaks, and silence when<br>
>> everything's alright.<br>
>><br>
> I also wanted this, and I ended up writing my own targets for it (it<br>
> includes other stuff such as callgrind and actual handling of the tests<br>
> themselves). The most recent iteration of it is available at:<br>
><br>
> git clone git://<a href="http://chasmd.org/chasmd.git" target="_blank">chasmd.org/chasmd.git</a><br>
><br>
> The cmake/test.cmake file is the one with the macros to create the<br>
> targets and example usage is in the test/ directory.<br>
><br>
> The output is dumped to files for easier reference rather than to the<br>
> terminal, but I'm sure a target that greps the logs for important<br>
> strings and errors on that wouldn't be hard to make.<br>
><br>
> Hope this helps.<br>
><br>
> --Ben<br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">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" target="_blank">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" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
<br>
</div></div>--<br>
Regards,<br>
<font color="#888888">-Clark<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">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" target="_blank">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" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br>