Peter Davies ultratwo@gmail.com writes:
@@ -79,6 +79,9 @@ my @ignores = ( "*.ok", "*.res", "*.so",
- "*.gcno",
- "*.gcov",
- "/conf*",
They are not generated by a standard build so they don't belong here. Put then in your local ignore file.
On 06/22/2010 11:03 AM, Alexandre Julliard wrote:
Peter Davies ultratwo@gmail.com writes:
@@ -79,6 +79,9 @@ my @ignores = ( "*.ok", "*.res", "*.so",
- "*.gcno",
- "*.gcov",
- "/conf*",
They are not generated by a standard build so they don't belong here. Put then in your local ignore file.
Is best practice to confine these to a particular folder (like you get with -fprofile-dir)? Is there a switch to do that for gcov data?
Thanks, Scott Ritchie
Is best practice to confine these to a particular folder (like you get with -fprofile-dir)? Is there a switch to do that for gcov data?
Due to limitations of my patch -fprofile-dir (or passing arguments to -fprofile-* is unsupported). All it allows you can do is pass "--coverage", "-fprofile-generate" or "-fprofile-use" to winegcc without arguments. It started as a hack to enable gcov and evolved into a hack to enable PGO and gcov.
Peter