August 2007 - Wine-Devel - list.winehq.org

Re: A script for automatic regression testing

by Vit Hrachovy

Hi Mikolaj, see winebot - a console Wine package tool for Windows programs for how to automate AutoHotkey installation for given wineprefix. http://winebot.sandbox.cz Regards Vit Mikolaj Zalewski wrote: > I wrote a small script that automates regression testing. It requires > an Autohotkey script that tests the program and creates a file > C:\Test-failed.txt if the test failed. The bash script will then do the > regression testing. It starts with copying the source tree and > wineprefix so it should be possible to do some normal work during > compilations. > At the beginning of the script there are some variables that needs to be > configured before running it. The wineprefix has to have Autohotkey > installed and associated with *.ahk. The attached script's settings will > find the regression for bug #9249. > If anyone is interested in it I'd be interested in some feedback. > > Mikołaj Zalewski

Aug. 11, 2007

Re: landfill.bugzilla.org?

by Roderick Colenbrander

On Saturday 11 August 2007 13:07, Dan Kegel wrote: > Why are all our new bugs cc'd to bugbot(a)landfill.bugzilla.org? > I suspect that's a default that needs to be removed... In the #winehackers channel there's now a bot which notifies of bugzilla changes. It could be related to that. Roderick

Aug. 11, 2007

landfill.bugzilla.org?

by Dan Kegel

Why are all our new bugs cc'd to bugbot(a)landfill.bugzilla.org? I suspect that's a default that needs to be removed...

Aug. 11, 2007

Re: Our wiki software is ugly

by AlexanderS

On Fri, 10 Aug 2007 15:05:58 -0700 Scott Ritchie <scott(a)open-vote.org> wrote: > Our wiki software needs a major update, especially as we start to > expect users to actually read it. > > For instance, look at the FAQ page: > > Then, click on edit and see how it should look. From what I can tell, > there are a few obvious errors: > Hi, btw. if you press preview on the edit page, it looks like it should xD Maybe its only a problem with the style of the final wiki page? Alexander > 1) The wiki software is completely ignoring line breaks. I could hit > return 4 times and the HTML rendered would be on subsequent lines, > without a break or paragraph tag between them. > 2) For some completely strange reason, if you make a list item that > includes a link then the entire list item will be in a smaller font. > This makes for extremely weird and inconsistent lists when a link to > another wiki page is included in some, but not all, of the items. > 3) Header text is almost impossible to figure out right, and there is > absolutely no standard of what we should do. > > Is there a reason we chose the software we did? Would it be too hard > to migrate to something else, or at least fix the display bugs? > > Thanks, > Scott Ritchie > > >

Aug. 11, 2007

re: Our wiki software is ugly

by Dan Kegel

Scott wrote: > ... > 3) Header text is almost impossible to figure out right, and there is > absolutely no standard of what we should do. [The amazing diversity in wiki syntaxes in the world makes me want to puke. Why not just use HTML syntax directly? It's at least well-defined.] Yeah, it's frustrating and looks bad. But at least the server is well-run :-) - Dan

Aug. 11, 2007

Re: [oleaut32/tests] Error when running tests on Wine, anyone?

by Clinton Stimpson

Stefan Leichter wrote: > Am Friday 10 August 2007 13:34 schrieb Paul Vriens: >> Hi, >> >> Can somebody confirm if all oleaut32 tests run correctly on Wine. I'm >> trying to change LoadLibrary to GetModuleHandle and though it was my >> failure, but current GIT fails for me: >> >> ../../../tools/runtest -v -P wine -M oleaut32.dll -T ../../.. -p >> oleaut32_test.exe.so vartest.c && touch vartest.ok >> fixme:variant:VarMod Could not convert left type 4096 to 20? rc == >> 0x80020008 fixme:variant:VarMod Could not convert left type 8192 to 20? rc >> == 0x80020008 fixme:variant:VarMod Could not convert left type 16384 to 20? >> rc == 0x80020008 vartest.c:3128: Test failed: got VT_DATE(-1.5) expected >> VT_DATE(-1.4) vartest.c:3129: Test failed: got VT_R8(-1.5) expected >> VT_R8(-1.4) >> vartest: 1031879 tests executed (0 marked as todo, 2 failures), 0 skipped. >> make: *** [vartest.ok] Error 2 >> >> Cheers, >> >> Paul. > > Hi, > > i get one error here too: > > sle(a)sle3:/usr/src/wine/wine-build$ make -C dlls/oleaut32/tests test > make: Entering directory `/usr/src/wine/wine-build/dlls/oleaut32/tests' > ../../../../wine-git/tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p > oleaut32_test.exe.so ../../../../wine-git/dlls/oleaut32/tests/vartest.c && > touch vartest.ok > fixme:variant:VarMod Could not convert left type 4096 to 20? rc == 0x80020008 > fixme:variant:VarMod Could not convert left type 8192 to 20? rc == 0x80020008 > fixme:variant:VarMod Could not convert left type 16384 to 20? rc == 0x80020008 > vartest.c:3129: Test failed: got VT_R8(-145) expected VT_R8(-1.4) > make: *** [vartest.ok] Fehler 1 > make: Leaving directory `/usr/src/wine/wine-build/dlls/oleaut32/tests' > > My system is an Athlon XP, Debian Etch > > Bye Stefan > > > Fails for me on AMD Opteron 270, gcc 4.1.1, FC6 x86_64 ../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p oleaut32_test.exe.so vartest.c && touch vartest.ok fixme:variant:VarMod Could not convert left type 4096 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 8192 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 16384 to 20? rc == 0x80020008 vartest.c:3128: Test failed: got VT_DATE(-1.5) expected VT_DATE(-1.4) vartest.c:3129: Test failed: got VT_R8(-1.5) expected VT_R8(-1.4) But passes for me on another computer with AMD Turion, gcc 4.1.2, FC7 i686 I copied oleaut32.dll.so from the working copy to non-working copy, and the test passed. Clint

Aug. 11, 2007

Re: WineD3D: Use the proper depth stencil format

by Chris Robinson

On Friday 10 August 2007 10:33:31 am Roderick Colenbrander wrote: > Hi, > > This patch lets WineD3D use the proper depth stencil format. The format is > retrieved from the WINED3DPRESENT_PARAMS. The proper format can improves > performance on platforms like Windows which offer more onscreen > pixelformats. > > Regards, > Roderick Colenbrander Isn't it normal to pass structs as a pointer, properly const-ified?

Aug. 11, 2007

Re: Thank you to Max Kanat -Alexander and Everything Solved

by Jolie Kanat

Dear Codeweavers and Wine people, Thank you for the great link. We wish you luck in all you do. Jolie Kanat Business Manager Everything Solved, Inc. 31 Adrian Terrace San Rafael, CA 94903 Fax: (650) 887-0377 http://www.everythingsolved.com/ Jeremy White wrote: > Say, > > I wanted to note that the Bugzilla upgrade is being done, by and > large, due to the very professional and helpful efforts > of Max Kanat of Everything Solved (www.everythingsolved.com) > > I don't know that I've ever seen Jeremy Newman *happy* about > Bugzilla, it's rather freaky <grin>. > > So, thanks! > > Cheers, > > Jeremy > > p.s. Yes, there are still kinks and issues with bugzilla; folks are working > furiously on #winehackers to iron out the worst of them right now.

Aug. 11, 2007

Fonts (+liberation again...)

by Louis. Lenders

Hi , a few weeks ago posted something about if liberation fonts could be included in wine. There didn't seem to be one view of how to do that. Of course 'winetricks liberation' is great, but i'd like to see something that works out of the box on a fresh .wine. Attached is a patch, that generates Arial.ttf from liberation font (just like winetricks) but this is an attempt to get it included in wine's source. To summarize, i added a file arial.ttf2sfd that changes a liberation font into "arial.sfd", change appropriate family/font name, and then generate the arial.ttf. All is done by fonforge. Of course this patch lacks checking for presence of liberation, and has ugly hard-coded path for the liberation-font, but that could be worked on later on. Simple question: Could something like this be included in the source, otherwise i'm not gonna spend any time improving it. Any hints welcomed. Regards, louis --------------------------------- Yahoo! Answers - Get better answers from someone who knows. Tryit now. diff --git a/Make.rules.in b/Make.rules.in index a32b276..257598e 100644 --- a/Make.rules.in +++ b/Make.rules.in @@ -126,7 +126,7 @@ LINTS = $(C_SRCS:.c=.ln) # Implicit rules -.SUFFIXES: .mc .rc .mc.rc .res .res.o .spec .spec.o .idl .tlb .h .y .l .tab.c .tab.h .yy.c .ok .sfd .ttf .man.in .man _c.c _i.c _p.c _s.c +.SUFFIXES: .mc .rc .mc.rc .res .res.o .spec .spec.o .idl .tlb .h .y .l .tab.c .tab.h .yy.c .ok .sfd .ttf .ttf2sfd .man.in .man _c.c _i.c _p.c _s.c .c.o: $(CC) -c $(ALLCFLAGS) -o $@ $< @@ -179,6 +179,9 @@ LINTS = $(C_SRCS:.c=.ln) .c.ok: $(RUNTEST) $(RUNTESTFLAGS) $< && touch $@ +.ttf2sfd.sfd: + $(FONTFORGE) -script $(TOPSRCDIR)/fonts/$< $< $@ + .sfd.ttf: $(FONTFORGE) -script $(TOPSRCDIR)/fonts/genttf.ff $< $@ diff --git a/configure b/configure diff --git a/dlls/gdi32/dc.c b/dlls/gdi32/dc.c diff --git a/dlls/shell32/shell32_En.rc b/dlls/shell32/shell32_En.rc diff --git a/dlls/shell32/shellpath.c b/dlls/shell32/shellpath.c diff --git a/dlls/shell32/shresdef.h b/dlls/shell32/shresdef.h diff --git a/dlls/user32/sysparams.c b/dlls/user32/sysparams.c diff --git a/fonts/Makefile.in b/fonts/Makefile.in index 2a69d6a..35d1e71 100644 --- a/fonts/Makefile.in +++ b/fonts/Makefile.in @@ -47,11 +47,16 @@ BITMAP_FONTS = \ vgas1257.fon \ vgas874.fon +TTF2SFD = \ + arial.sfd + TRUETYPE_FONTS = \ - marlett.ttf + marlett.ttf \ + arial.ttf FONTS = \ $(BITMAP_FONTS) \ + $(TTF2SFD) \ $(TRUETYPE_FONTS) all: $(FONTS) diff --git a/fonts/arial.ttf2sfd b/fonts/arial.ttf2sfd new file mode 100644 index 0000000..2ce704e --- /dev/null +++ b/fonts/arial.ttf2sfd @@ -0,0 +1,3 @@ +Open("/usr/share/fonts/liberation/LiberationSans-Regular.ttf"); +SetFontNames("ArialMT", "Arial", "Arial"); +Generate($2); diff --git a/include/setupapi.h b/include/setupapi.h diff --git a/tools/wine.inf b/tools/wine.inf

Aug. 10, 2007

Our wiki software is ugly

by Scott Ritchie

Our wiki software needs a major update, especially as we start to expect users to actually read it. For instance, look at the FAQ page: Then, click on edit and see how it should look. From what I can tell, there are a few obvious errors: 1) The wiki software is completely ignoring line breaks. I could hit return 4 times and the HTML rendered would be on subsequent lines, without a break or paragraph tag between them. 2) For some completely strange reason, if you make a list item that includes a link then the entire list item will be in a smaller font. This makes for extremely weird and inconsistent lists when a link to another wiki page is included in some, but not all, of the items. 3) Header text is almost impossible to figure out right, and there is absolutely no standard of what we should do. Is there a reason we chose the software we did? Would it be too hard to migrate to something else, or at least fix the display bugs? Thanks, Scott Ritchie

Aug. 10, 2007