Re: [RESEND 2] Changes to enable the use of gcov and PGO

2010-06-16 Thread Peter Davies
>LDFLAGS are already passed to winegcc where appropriate. Oops, hadn't noticed they got in though $(ALL_LIBS), you can omit that part of the patch then. Why do we silently drop unrecognized args in "winegcc" anyway? Peter

Re: [RESEND 2] Changes to enable the use of gcov and PGO

2010-06-16 Thread Alexandre Julliard
Peter Davies writes: > @@ -72,7 +72,7 @@ MAKECTESTS = $(TOOLSDIR)/tools/make_ctests$(TOOLSEXT) > WRC = $(TOOLSDIR)/tools/wrc/wrc$(TOOLSEXT) > WMC = $(TOOLSDIR)/tools/wmc/wmc$(TOOLSEXT) > WIDL = $(TOOLSDIR)/tools/widl/widl$(TOOLSEXT) > -WINEGCC = $(TOOLSDIR)/too

Re: Changes to enable the use of gcov

2010-06-15 Thread Peter Davies
> Somehow this patch got munged in transit and will not apply to current git. > Can you update it and send it again? I think my mail client (gmail) line wraps. I discovered when trying to apply it myself. > As an aside, if gcov compilation finally starts working that means we > can build Wine u

Re: Changes to enable the use of gcov

2010-06-14 Thread Scott Ritchie
On 06/14/2010 08:04 PM, James McKenzie wrote: > Peter Davies wrote: >> To use gcov you must pass --coverage at both compile and link time. >> This patch means that "make CFLAGS=--coverage LDFLAGS=--coverage", >> "make test", >> "gcov file.c" is sufficient generate .gcov files. >> >> > Peter: >

Re: Changes to enable the use of gcov

2010-06-14 Thread James McKenzie
Peter Davies wrote: To use gcov you must pass --coverage at both compile and link time. This patch means that "make CFLAGS=--coverage LDFLAGS=--coverage", "make test", "gcov file.c" is sufficient generate .gcov files. Peter: Somehow this patch got munged in transit and will not apply to cur