GNOME Bugzilla – Bug 764075
Do not enable code coverage unconditionally
Last modified: 2016-03-23 15:21:48 UTC
See patch.
Created attachment 324591 [details] [review] build: Do not enable code coverage based on lcov Code coverage turns on various slow paths and disables optimizations. It should be, and it usually is, an opt in configuration flag. Enabling it should not be conditional on the existence of the lcov binary on the system, otherwise anybody building PyGObject from Git on any moderately complete development environment will automatically enable code coverage even when not wanted.
This commit partially reverts commit 0456d9c8 — I could not do a full revert because the autogen.sh file has been modified since 2012.
I was wondering why I never hit this case and turns out passing arguments when sourcing only works in bash. As debian uses dash for sh EXTRA_ARGS never gets passed anyway (not sure about fedora..).
Review of attachment 324591 [details] [review]: lgtm
Attachment 324591 [details] pushed as 6ff29c9 - build: Do not enable code coverage based on lcov