Hi. A while ago (2004), there was some work about wine with gcov, with the focus on "Picassa 2": ( http://www.cs.hmc.edu/clinic/projects/2004/google/ ) Final Report: ( http://www.cs.hmc.edu/clinic/projects/2004/google/final_report/main.pdf ) It would be nice, when we can support gcov in current Wine "out of the box". That would help us a lot, when we write more tests for the suggested Wine 1.0 Applications. GCOV: http://gcc.gnu.org/onlinedocs/gcc/Gcov.html -- By by ... Detlef
On 10/12/07, Detlef Riekenberg <wine.dev(a)web.de> wrote:
A while ago (2004), there was some work about wine with gcov, with the focus on "Picassa 2": ( http://www.cs.hmc.edu/clinic/projects/2004/google/ )
Final Report: ( http://www.cs.hmc.edu/clinic/projects/2004/google/final_report/main.pdf )
It would be nice, when we can support gcov in current Wine "out of the box". That would help us a lot, when we write more tests for the suggested Wine 1.0 Applications.
That project had a doc patch accepted: http://www.winehq.org/pipermail/wine-patches/2005-April/017067.html This created http://www.winehq.org/site/docs/winedev-guide/x1374 Does that suffice? It doesn't give a global report, but that's probably ok. - Dan
On 10/12/07, Dan Kegel <dank(a)kegel.com> wrote:
On 10/12/07, Detlef Riekenberg <wine.dev(a)web.de> wrote:
A while ago (2004), there was some work about wine with gcov, with the focus on "Picassa 2": ( http://www.cs.hmc.edu/clinic/projects/2004/google/ )
Final Report: ( http://www.cs.hmc.edu/clinic/projects/2004/google/final_report/main.pdf )
It would be nice, when we can support gcov in current Wine "out of the box". That would help us a lot, when we write more tests for the suggested Wine 1.0 Applications.
That project had a doc patch accepted: http://www.winehq.org/pipermail/wine-patches/2005-April/017067.html This created http://www.winehq.org/site/docs/winedev-guide/x1374 Does that suffice? It doesn't give a global report, but that's probably ok. - Dan
This information should be in the Wiki somewhere. -- James Hawkins
On 10/12/07, James Hawkins <truiken(a)gmail.com> wrote:
This information should be in the Wiki somewhere.
Yes, we should remove all web pages from the entire web and put them in a wiki. - Dan
On Fri, 2007-10-12 at 10:01 -0700, Dan Kegel wrote:
Yes, we should remove all web pages from the entire web and put them in a wiki.
I think he meant that at least a link should be made from the Wiki :) This is developer's info, and I think most developers rather use the wiki than the other types of documentation. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On 10/12/07, Dimi Paun <dimi(a)lattica.com> wrote:
This is developer's info, and I think most developers rather use the wiki than the other types of documentation.
I think the real problem is that the website uses a template system that is hard to preview. The advantage of the wiki is that previewing is easy. The disadvantages of the wiki are a) it's not stored in git b) there's no way to do local editing and previewing c) the formatting is crap It'd be nice to have the best of both worlds, i.e. a wiki backed by git, and written in such a way that users who preferred to avoid online editing could use git to edit it locally, using an easy local preview tool, with strong formatting capabilities (like html) instead of the unhappy situation we have now, where formatting is an unreliable mystery. The other good thing about our wiki is that it has very good uptime and performance (thanks Dimi). - Dan
On Fri, 2007-10-12 at 10:47 -0700, Dan Kegel wrote:
It'd be nice to have the best of both worlds, i.e. a wiki backed by git, and written in such a way that users who preferred to avoid online editing could use git to edit it locally, using an easy local preview tool, with strong formatting capabilities (like html) instead of the unhappy situation we have now, where formatting is an unreliable mystery.
Yes, I've been dreaming for a long time after such a system. There is a wiki out there that uses git as backend, I forget the name now. But they need more maturing. As for formatting, you don't want to be too crazy, HTML is powerful but also verbose, a wiki needs terse syntax, and that often comes at the expense of seldom used formatting power. That being said, I agree that it could be done a bit better than what we have now.
The other good thing about our wiki is that it has very good uptime and performance (thanks Dimi).
Thank you Dan, I'm really glad to see people use it, and they enjoy the experience. My hope is that it will become even better going forward. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
Dimi Paun wrote:
On Fri, 2007-10-12 at 10:47 -0700, Dan Kegel wrote:
It'd be nice to have the best of both worlds, i.e. a wiki backed by git, and written in such a way that users who preferred to avoid online editing could use git to edit it locally, using an easy local preview tool, with strong formatting capabilities (like html) instead of the unhappy situation we have now, where formatting is an unreliable mystery.
Yes, I've been dreaming for a long time after such a system. There is a wiki out there that uses git as backend, I forget the name now. But they need more maturing. As for formatting, you don't want to be too crazy, HTML is powerful but also verbose, a wiki needs terse syntax, and that often comes at the expense of seldom used formatting power. That being said, I agree that it could be done a bit better than what we have now.
Make no mistake, what we have now is crap. It's a shame we show it to users when it's so laden with display bugs.
The other good thing about our wiki is that it has very good uptime and performance (thanks Dimi).
Thank you Dan, I'm really glad to see people use it, and they enjoy the experience. My hope is that it will become even better going forward.
The wiki is still, however, amazingly awesome. Thank you, you're really on top of it :) Thanks, Scott Ritchie
On Fri, 2007-10-12 at 12:00 -0700, Scott Ritchie wrote:
Make no mistake, what we have now is crap. It's a shame we show it to users when it's so laden with display bugs.
I'm afraid I don't understand -- what is crap, and where are the display bugs? -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On 10/12/07, Dimi Paun <dimi(a)lattica.com> wrote:
On Fri, 2007-10-12 at 12:00 -0700, Scott Ritchie wrote:
Make no mistake, what we have now is crap. It's a shame we show it to users when it's so laden with display bugs.
I'm afraid I don't understand -- what is crap, and where are the display bugs?
Font sizes change randomly based on previous lines. It's unpredictable.
On Fri, 2007-10-12 at 13:11 -0700, Dan Kegel wrote:
Font sizes change randomly based on previous lines. It's unpredictable.
True, but I'd argue that "total crap" is a bit harsh. In any event, this has nothing to do with the Wiki. It generates correct HTML (if anyone notices any problems, I'd be happy to fix it, but I've seen none AFAICT). The problem is with CSS + browsers. This is a nasty problem that is hard to deal with, no matter where you store the data. If people can help with the CSS problem, it would be much appreciated. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On Fri, 12 Oct 2007, Dan Kegel wrote: [...]
The disadvantages of the wiki are a) it's not stored in git b) there's no way to do local editing and previewing c) the formatting is crap
d) there's no way to translate it -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Indifference will certainly be the downfall of mankind, but who cares?
On Sat, 2007-10-13 at 10:32 +0200, Francois Gouget wrote:
d) there's no way to translate it
http://moinmoin.wikiwikiweb.de/HelpOnLanguages More is on the way I believe. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On Sat, 13 Oct 2007, Dimi Paun wrote:
On Sat, 2007-10-13 at 10:32 +0200, Francois Gouget wrote:
d) there's no way to translate it
http://moinmoin.wikiwikiweb.de/HelpOnLanguages
More is on the way I believe.
Ok. So I have added a FoireAuxQuestions page with the start of a translation for the FAQ. http://wiki.winehq.org/FoireAuxQuestions I have also added a FrenchDict page as described in the above help, in an attempt to have users who open the FAQ page sent to the FoireAuxQuestions page if their locale is French. However this does not seem to work. Do you know what I got wrong? Another issue I have is: after some time, how do I know which parts of the translation are up to date and which are not? The above page does not touch on this issue. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ It really galls me that most of the computer power in the world is wasted on screen savers. Chris Caldwell from the GIMPS project http://www.mersenne.org/prime.htm
On Sat, 2007-10-13 at 19:02 +0200, Francois Gouget wrote:
I have also added a FrenchDict page as described in the above help, in an attempt to have users who open the FAQ page sent to the FoireAuxQuestions page if their locale is French. However this does not seem to work. Do you know what I got wrong?
I'm afraid not, I've never used the feature. I guess you can ask the MoinMoin guys, they are usually responsive.
Another issue I have is: after some time, how do I know which parts of the translation are up to date and which are not? The above page does not touch on this issue.
I don't think they have anything builtin, but you can always ask. At the very least, one can store the version of the translated page in a comment at the top of the page, and keep track of differences that way... -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On Fr, 2007-10-12 at 09:47 -0700, Dan Kegel wrote:
It would be nice, when we can support gcov in current Wine "out of the box". That would help us a lot, when we write more tests for the suggested Wine 1.0 Applications.
That project had a doc patch accepted: http://www.winehq.org/pipermail/wine-patches/2005-April/017067.html This created http://www.winehq.org/site/docs/winedev-guide/x1374 Does that suffice?
I was thinking about: "./configure --enable-gcov" or "./configure --with-gcov" With the suggested flags, wine does not compile: gcc -c -I../../../src/dlls/activeds -I. -I../../../src/include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -fprofile-arcs -ftest-coverage -o activeds_main.o ../../../src/dlls/activeds/activeds_main.c ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ../../../src/dlls/activeds/activeds.spec activeds_main.o -o activeds.dll.so -lkernel32 ../../libs/port/libwine_port.a activeds_main.o: In function `global constructors keyed to 0_DllMain':activeds_main.c:(.text+0x6da): undefined reference to `__gcov_init' activeds_main.o:(.data.rel+0x24): undefined reference to `__gcov_merge_add' ../../dlls/winecrt0/libwinecrt0.a(stub.o): In function `global constructors keyed to 0___wine_spec_unimplemented_stub':stub.c:(.text +0x81): undefined reference to `__gcov_init' ../../dlls/winecrt0/libwinecrt0.a(stub.o):(.data.rel+0x24): undefined reference to `__gcov_merge_add' collect2: ld gab 1 als Ende-Status zurück winegcc: gcc failed. make[2]: *** [activeds.dll.so] Fehler 2 make[1]: *** [activeds] Fehler 2 make: *** [dlls] Fehler 2 -------- I tried also: export CFLAGS="-fprofile-arcs -ftest-coverage" ./configure that breaks wine already in tools/* -- By by ... Detlef
participants (7)
-
Dan Kegel -
Dan Kegel -
Detlef Riekenberg -
Dimi Paun -
Francois Gouget -
James Hawkins -
Scott Ritchie