[CMake] Code coverage under Windows

[felix.morency at gmail.com]

David,

Thank you for your answer. I don't know much about Visual Studio code  
coverage, but it seems to be a new feature of VS 2010. I never tested it.  
You can find more information at

http://msdn.microsoft.com/en-us/library/ms182496.aspx

However, only 32bits applications seems supported. More informations on how  
to configure code coverage can be found at

http://msdn.microsoft.com/en-us/library/dd504821.aspx

Regards,
-Félix C. Morency

On Feb 14, 2011 12:23pm, David Cole <david.cole at kitware.com> wrote:
> On Mon, Feb 14, 2011 at 11:09 AM, felix.morency at gmail.com> wrote:

> Hi,

> On the wiki, it is mentioned that code coverage is supported using gcov  
> and Bullseye. However on the CMake dashboard, under the code coverage  
> section, you can see that the build name for the "dash22.kitware" site  
> is "Win32-vs9-Release-Coverage". I wondered if this site is using Bulleye  
> or if it uses the MSVC code coverage tools/informations. If using  
> Bullseye, are there any plans on supporting MSVC code coverage  
> informations on the way? If using MSVC code coverage, is there any piece  
> of information on how we can achieve this using CTest/CDash?


> Regards,
> -Félix C. Morency
> _______________________________________________

> 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




> dash22 uses Bullseye for its coverage data.



> What do you mean when you say "MSVC code coverage" -- where can we find  
> out more about how to support it? I didn't even know there were any  
> built-in code coverage tools in Visual Studio.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20110214/b6852aa3/attachment.htm>