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

Re: Excluding a Windows version from the tests

by Paul Vriens

Alexandre Julliard wrote: > Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > >> yesterday a patch of mine was committed to test more profile stuff >> from kernel32. When I have a look now at test.winehq.org I see that >> some test(s) crash on win98 but not on others. >> >> Although I could use a if(0) construction (as is done in several other >> tests), I'm wondering if we should just not run specific tests on >> specific Windows versions. It's a shame that one OS version blocks the >> running of several other tests. > > In general, if a feature crashes on Windows it's unlikely that an app > would depend on it, so it's not a problem to disable or remove the > test. > But in this case we're dealing with win98 which new apps will not support anymore! I'll create a new patch to disable (with comments) the failing tests. Cheers, Paul.

March 29, 2007

Re: Is Wine a platform for Codeweaver to make money?! Please help me understand.

by Stefan Dösinger

Hi, Getting common applications working is NOT the goal of wine. The goal of wine is to write an open source reimplementation of the Win32 api. Those two goals are related, but not exactly the same. The difference is how to deal with hacks that are known to be incorrect but happen to fix an application. Those are not accepted into wine, no matter which application they fix. CrossOver uses Wine under its hood, and CrossOver's wine tree contains some hacks to make Microsoft Office and other popular applications happy. However, CodeWeavers contributes patches back and employs many major developers to work on various parts of wine, including Alexandre Julliard, Robert Shearman, Jakec Caban, me, and many others. Neither Wine nor CrossOver are specifically targeted at games or office applications. CrossOver supports some games(like Half-Life 1 and 2, World of Warcraft, Prey), and my job is to work on Wine's Direct3D support. I won't be able to convice you that the whole thing is not a conspicary because I am a codeweavers employee, but maybe searching the wine changelog for @codeweavers.com can convice you? (Though many codeweavers employees use their own private mail address to send patches). Regarding the hacks to get Microsoft Office running, the modified Wine source in CrossOver is publically available at http://www.codeweavers.com/products/source . You are welcome to locate the hacks that fix Microsoft Office(I think their authors will kindly assist you with that), clean them up and send them to wine-patches for inclusion. (on a sidenode, a few weeks ago I noticed that some mirror had a broken copy of the archive which did not unpack completely. I think it should be fixed by now. So if the archive doesn't unzip its not conspiracy, it is a fault of the provider of our mirrors) Hope my explanations answer your questions, Stefan

March 29, 2007

Re: Excluding a Windows version from the tests

by Alexandre Julliard

Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > yesterday a patch of mine was committed to test more profile stuff > from kernel32. When I have a look now at test.winehq.org I see that > some test(s) crash on win98 but not on others. > > Although I could use a if(0) construction (as is done in several other > tests), I'm wondering if we should just not run specific tests on > specific Windows versions. It's a shame that one OS version blocks the > running of several other tests. In general, if a feature crashes on Windows it's unlikely that an app would depend on it, so it's not a problem to disable or remove the test. -- Alexandre Julliard julliard(a)winehq.org

March 29, 2007

Re: Is Wine a platform for Codeweaver to make money?! Please help me understand.

by Bryan Haskins

Well a lot of gamers use wine, wine is meant to be a general "run this windows app" program where as Codeweavers, and Cedega work case by case with teams to get specific apps working. If you have a bug, submit it, otherwise add data to bugs in the DB, and eventually it will all work out. On 3/28/07, Sasan Iman <iman(a)simantis.com> wrote: > > > > First of all, let me say that I am not a developer. But I have been > interested in Wine since early 2003. The thing that has always made me > scratch my head is that the Windows software that motivates me to > install Wine on my linux system (i.e. MS OFfice, etc.) has never worked > with wine in a reliable manner. Meanwhile, Codeweaver has always had MS > Office working on Wine. > > Now shouldn't getting the most common windows software working on Wine > in an idiot-proof (meaning I can get it to work) manner be the highest > priority for Wine developers? Instead, this is left to CodeWeavers and > others. > > I know that if you fiddle around with the stock release long enough you > can get MS Office working on Wine as I have on a number of occasions, > but shouldn't making this work for everyone be the highest priority for > getting Wine to be adopted more widely?! Or is Wine more targeted to > gamers which is mostly what I read about on WineHQ? > > I just can't understand why the more common application are left to a > commercial company. My conspiratorial side makes me want to think this > is a conspiracy but I am sure there is valid technical and logistical > reasons for it so I am asking you guys. > > Thanks. > > Sasan > > > > > > -- Cheers, Bryan

March 29, 2007

Re: Is Wine a platform for Codeweaver to make money?! Please help me understand.

by Felix Nawothnig

Sasan Iman wrote: > I know that if you fiddle around with the stock release long enough you > can get MS Office working on Wine as I have on a number of occasions, > but shouldn't making this work for everyone be the highest priority for > getting Wine to be adopted more widely?! Or is Wine more targeted to > gamers which is mostly what I read about on WineHQ? My guess: Wine is not a product so it's not targeted to anyone. It's a community project developed by volunteers - and the primary priority of those volunteers is to get Wine to run the applications they want to use. Since there are many nice free & libre cross-platform alternatives to the MS office suite there is just not much incentive to get it to run or keep it running. Games OTOH... Felix

March 29, 2007

Re: gdi32: Add failing metrics test for negative font widths

by Alexandre Julliard

Felix Nawothnig <flexo(a)holycrap.org> writes: > Felix Nawothnig wrote: >> --- >> dlls/gdi32/tests/font.c | 37 +++++++++++++++++++++++++++++++++++++ >> 1 files changed, 37 insertions(+), 0 deletions(-) > > Anything wrong with this patch? It fails here: ../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so font.c && touch font.ok font.c:541: Tests skipped: Symbol is not installed so skipping this test font.c:784: Tests skipped: Arial is not installed font.c:1094: Tests skipped: Arial is not installed font.c:1228: Tests skipped: Arial Black is not installed font.c:1228: Tests skipped: Symbol is not installed font.c:1682: Tests skipped: Arial Black or Symbol/Wingdings is not installed font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1513: Test failed: Expected 00000031, got 00000002 font.c:1515: Test succeeded inside todo block: Expected 00000000, got 00000000 font.c:1517: Test succeeded inside todo block: Expected 0000003d, got 0000003d font.c:1513: Test failed: Expected 0000004d, got 00000001 font.c:1513: Test failed: Expected 0000000d, got 00000001 font.c:1513: Test failed: Expected 0000001c, got 00000001 font.c:1513: Test failed: Expected 00000047, got 00000002 make: *** [font.ok] Error 17 -- Alexandre Julliard julliard(a)winehq.org

March 29, 2007

Re: Allow enabling/disabling Direct3D usage of GLSL in Winecfg + update Czech locales for Winecfg

by Stefan Dösinger

Am Mittwoch 28 März 2007 23:09 schrieb Vit Hrachovy: > Hi Stephan, > GLSL depends on Czech localization update. > Should I split them into two separate patches with different numbers? > Should I send them split in two different requests? > Regards Send the localization update first, then GLSL. Number the patches, for example [1/2] winecfg: czech localization update [2/2] winecfg: add d3d options You can send them at once, but in different mails

March 29, 2007

Re: Question about OpenAL

by Dennis Schridde

Am Donnerstag, 29. März 2007 schrieb Mike Schaadt: > Is there any interest in adding OpenAL to Wine? I would imagine it's > relatively simple to implement the OpenAL dll that would be a simple > wrap around the Linux OpenAL library assuming they have the same > functionality(from what I know of OpenAL, they should). > > It's not a very common library, but if we could implement it on top of > the local implementation, that would mean that programs that use it > would be using local devices without having to go through the > DirectSound library. > > I'm not talking about using OpenAL as an audio driver, but an > implementation of the OpenAL library for Wine that would use the local > version of OpenAL. I tried looking around, and the only thing I found > was talk about the OpenAL driver, and also brief requests for an > OpenAL dll, but I didn't see anything official. > > Any thoughts on if this is something that would be beneficial to add? See this link for to the associated bug: http://bugs.winehq.org/show_bug.cgi?id=7142 There is also a link to the discussion of a patch. I don't know how this progressed, though. --Dennis

March 29, 2007

Re: Question about OpenAL

by Jan Zerebecki

On Thu, Mar 29, 2007 at 10:38:26AM -0500, Mike Schaadt wrote: > Is there any interest in adding OpenAL to Wine? I would imagine it's > relatively simple to implement the OpenAL dll that would be a simple > wrap around the Linux OpenAL library assuming they have the same > functionality(from what I know of OpenAL, they should). There is interest and there was an implementation posted to this list (and/or possibly -patches) that worked fine for some people. But it seems for the time being it isn't further pursued by the author. Jan

March 29, 2007

Re: Question about OpenAL

by Stefan Dösinger

Am Donnerstag 29 März 2007 17:38 schrieb Mike Schaadt: > Is there any interest in adding OpenAL to Wine? I would imagine it's > relatively simple to implement the OpenAL dll that would be a simple > wrap around the Linux OpenAL library assuming they have the same > functionality(from what I know of OpenAL, they should). Such a DLL was written already by nick burns, but not yet accepted into wine because it broke applications using openal and wasn't ready for prime time yet. Seach the wine-patches archives for "openal thunk". I think there was consent that a thunk should go in, but a driver comparably to our alsa backend shouldn't. Some stuff google finds: Oldest version: http://www.winehq.org/pipermail/wine-devel/2006-November/052501.html My first mail with a simmilar suggestion: http://www.archivesat.com/Wine_Developers_list/thread2111847.htm Some more updated patch: http://www.winehq.org/pipermail/wine-patches/2006-November/033205.html The latest patch I could find: http://www.winehq.org/pipermail/wine-patches/2007-January/034454.html

March 29, 2007