[Bf-committers] Compiling w/ Code Coverage
jason.a.wilkins at gmail.com
Thu Oct 18 19:57:06 CEST 2012
I made some headway towards creating a WITH_CODE_COVERAGE option
yesterday. The only problem I had seemed to be that programs like
makesrna, makesdna, and datatoc use the same options but not the same
libraries. Also the fact that Xcode now defaults to using clang. My
solutions to both of these problems is kind of hackish, but if I get
things working it should be fairly small patch. (I'd leave it to an
interested party who uses Scons to port it over).
My use for it is to make sure I've tested every part of the OpenGL
abstraction layer I created for GSoC. I figured I'd invest time in
getting code coverage enabled rather than fussing around with other
methods I might try that would end up being wasted.
As for performance, it appears to not have much impact so far.
On Wed, Oct 17, 2012 at 11:41 PM, Campbell Barton <ideasman42 at gmail.com> wrote:
> never used gcov, but did use valgrind for this through qtcreator /
> kcachegrind on linux you can see line-by-line times and callgraphs.
> number of calls... etc.
> Its really slow and at the time I didn't have much of a use for it.
> On Wed, Oct 17, 2012 at 7:04 AM, Jason Wilkins
> <jason.a.wilkins at gmail.com> wrote:
>> I'm going to take the lack of response as a "No" and go ahead and
>> figure out how to modify the CMake build to do this for me.
>> On Sun, Oct 14, 2012 at 6:39 PM, Jason Wilkins
>> <jason.a.wilkins at gmail.com> wrote:
>>> Has anybody ever attempted to and gotten code coverage to work when
>>> compiling Blender? I want to use gcov for some testing, but I did not
>>> want to duplicate any work.
>> Bf-committers mailing list
>> Bf-committers at blender.org
> - Campbell
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers