- Wine-Devel - list.winehq.org

Re: Wine and Intel Macs
by Steven Edwards Feb. 9, 2006

Feb. 9, 2006

Hi, On 2/8/06, Eric W. Triplett <ewt(a)ufl.edu> wrote: > Does Wine work with the new Macs that contain Intel processors? If > so, which distribution should I download and install? It should compile out of the box. Beware you may need a few patches from the darwine mailing list to get some win32 apps running. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

1 0

Somewhat disappointing experiences with Winelib and WTL
by Claus Fischer Feb. 8, 2006

Feb. 8, 2006

Hi Wine developers and users! Over the last few days, I have been trying to find out whether the combination of WTL and Winelib could be a promising inter-platform GUI solution. While I have made some progress and got some new knowledge, I believe I have now come to a dead end where I'll have to give up that attempt. In case you are interested, here's my summary report. It might be useful to others. Regards, Claus *********************************************************** The Goal: ********* WTL on Windows gives me: - compact executables: small and fast - easy-to-install executables: no DLLs needed - programs easy to maintain and deploy - mature GUI The goal is to combine WTL/ATL (no COM) with Winelib to create a Linux-application with the same look and feel and roughly the same qualities: no DLL's, shared libraries, C++ ABI hassles, etc. Just one binary linked to libc. 1. ATL/WTL ********** ATL 3.0 (from my MSVC 6 compiler) and WTL 7.5 (from sourceforge) can be made to work. Issues are: - GCC 4 is very picky with templates and would need lots of template prototypes; I have used GCC 3.3.5 - Some template prototypes are still needed - Some MSVC-specific pragmas etc. need to be ifdef'd - A few pack pragmas need to be replaced by Wine's pack headers - Everything related to _get_uuid(class) I've commented out; I need no COM stuff - Some GCC warnings need to be turned off, or alternatively code changes need to be made - Various small changes - As more parts of WTL get used (i.e. instantiated), more changes will be required Basically, ATL+WTL can reach a state where they compile with GCC 3 and the changes are still mostly cosmetic. Some of the changes might even be incorporated in the official WTL, now that it's free. I have read the mails of Boaz Harrosh' previous changes; apparently he has had to invest much more work because of COM. With the modified ATL/WTL, I was able to compile the wizard-created sample SDI application on Linux. 2. Winelib "as is" ****************** After some digging through the Web, I've been able to link the sample SDI application against Winelib. It took somewhat longer than it should have due to (a) WTL's habit of just ATLASSERT()ing things and (b) the rather elaborate work of finding those places with wine-dbg and/or ATLTRACE()s plus WINEDEBUG=+relay. Since I'm not familiar with the Wine debugger, it would have been very helpful to be able to use gdb on the resulting executable. However, gdb reported that it didn't know the file format. ==> Wishlist to Wine: - Make gdb work on Winelib programs - Document Winelib and the build process better (the documentation is outdated, though the tools are good). All in all a reasonably successful endeavour, and the application runs stable and looks fine except for the font (that probably can be configured better). BUT: ... BIG SHOCK: That's not a single ELF executable, it's a weird mixture of PE and ELF and a .so file and a wrapper program that apparently starts wine in the background ... That doesn't fulfill my goals of building a native Linux exe with no dependencies except libc. It's also quite slow when loading. 3. Winelib statically linked **************************** Apparently Wine has made a decision a few years ago: that support for native Windows apps with all the infrastructure they need (Wine server, registry, resources, multithreading, etc.) is more important than support for porting applications to native Linux apps. That decision is obviously correct, given the large number of Windows applications that are only available as binaries and require much infrastructure. I'm aware of that, but I've still decided to give my dream of a native Linux app a try. I tried the following method: (a) Get and compile Wine 0.9.7 (b) Add rules to Makedll.rules to pack the objects into .a libraries (c) Attempt to link my program's objects against those static libs (d) Make changes and corrections and repeat I first made a reduced WTL application that does not use a resource file. I don't know if this was a good decision. The following changes were necessary to Wine: - Comment out a lot of DLLMain functions - Comment out some 16-bit functions that have name collisions - Turn on debug mode (-O0 -g) - Write a startup function main() (Wine's libwinecrt0.a didn't work for me) That might be the reason for more trouble - Link to all of libs/unicode - Link to some objects in libs/wine (I didn't link to loader, don't know if that's good) This is where the heavy trouble started: - Replace the assembly stuff in critical sections (due to the debug mode) ... my app is single-threaded - Somehow set up code pages for ansi/Unix (LocaleInit() failed, see below) - Comment out some calls to the registry where the run-time environment is registered What eventually caused me to stop is: - Somehow fake Wine Server or do the equivalent stuff or just jump over (Basically Register Class as atoms) - Somehow fake a lot of initial resources (E.g. GetSystemCursor etc.) - Overall too many modifications in interacting systems - Altogether not a "robust" feeling This is where I stopped. I don't know whether I'm "so close" or miles away, but my random code editing seemed to get out of hand. 4. What is needed ***************** What would be needed to support static linking against Winelib (if that's decided to be a supportworthy goal): - Infrastructure to build static libs - separate out DllMain - separate out some 16 bit functions - Possibility to provide heap based allocation through straight malloc() - Infrastructure to fake loading resources (for those resources that come from Winelib/system) - Infrastructure for proper initialization of modules e.g. through one setup function for each DLL and one common setup function that calls the others in some natural order The overall initialization function should be configurable so that programs that need only a few DLL's (user, gdi, crtdll, kernel, ntdll) don't need to link everything - Infrastructure to allow faking registry calls for those calls initiated by Winelib internal stuff (and possibly also ATL/WTL internal stuff) - Infrastructure to handle Window class registration etc. (i.e. reduced Wine server support in the app) What I specifically don't need/want through Winelib: - networking - filesystem access - loading of external DLL's or other libraries - C++ runtime library support *********************************************************** This is, in keywords, my experience with WTL and static Winelib linking. I'll be apreciative of any responses. Please CC: my mail address. Also, if anyone is interested in hosting patches to ATL/WTL or even just looking at them, I'll gladly provide them. Regards, Claus -- Claus Fischer <claus.fischer(a)clausfischer.com> http://www.clausfischer.com/

6 10

Wine and Intel Macs
by Eric W. Triplett Feb. 8, 2006

Feb. 8, 2006

Does Wine work with the new Macs that contain Intel processors? If so, which distribution should I download and install? Thanks, Eric -- ___________________________________________ Professor Eric W. Triplett, Chair Department of Microbiology and Cell Science Institute of Food and Agricultural Sciences University of Florida P.O. Box 110700 Gainesville, FL 32611-0700 1-352-392-5430 (phone) 1-352-392-5922 (fax) ewt(a)ufl.edu ___________________________________________

1 0

gethostbyname call with 0 length arg
by Phil Goss Feb. 8, 2006

Feb. 8, 2006

Hi, Is it a bug in the WINE gethostbyname (WS_gethostbyname) implementation, where if the arg name is of string length 0, then it returns unsuccessful. I have experience this issue with a Windows program (Onkyo Nettune) where the hostname passed to gethostbyname is of length 0. (This seems to be a bug in the program itself). However, the program works okay in native Windows. There seems to be a check in the gethostbyname for a NULL arg name ... if(!name) ... But no check for ... if(!strlen(name)) .... I have tested the strlen check and it seems to work and satisfies the Windows program. Does the above make sense, as I am not a programmer? Not sure if this s bug in wine even though it implementation should be matching Windows native. Thanks, Phil -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

4 9

Wine with multiple threads on Dual processor - any suggestions please
by Ananth M Feb. 8, 2006

Feb. 8, 2006

Hi, I am having an application with the processing can be done paralally using multiple threads. If I compile (with one thread ) and execute this application in Linux , on a Dual processor machine , I am getting execution time ~600 sec. If I compile ( with 2 threads ), and execute this application in Linux on a Dual processor machine , I am getting execution time ~300 sec. If I compile the same program (with One thread) using wineg++ and execute the program ,I am getting execution time as ~500 sec If I compile the same program ( with 2 threads ) using wineg++ and execute the program , I am getting the same execution time ~500 sec. Is there any isses with wine on Dual processor machines ( Intel Xeon processor ) w.r.t multi threaded programming? Does any one got this type of problem ? Any suggestions please.... Thank you, Regards Ajay

1 0

Re: VC++ demangling tool
by Eric Pouech Feb. 8, 2006

Feb. 8, 2006

Michael Stefaniuc wrote: > Hello! > > winedump has a VC++ symbol demangling function but that is bitrotting as > it is a copy of the msvcrt.__unDname . As i wanted to use the newer > msvcrt.__unDname funtion i have written a quick and dirty program that > is basicaly only a wrapper around UnDecorateSymbolName(). Most importand > feature is that it runs on the command line. > I'm not expecting it to go into Wine but others might find it usefull. > After applying the patch configure needs to be regenerated. actually, there's a tool in the MS SDK called undname that does exactly this... it has also a couple of other options (like demangling all symbols listed in a text file)... but what should be done is to port back the code from msvcrt into winedump A+ -- Eric Pouech

6 8

Re: Add missing LANG_xxx and SUBLANG_xxx macros
by Alexandre Julliard Feb. 8, 2006

Feb. 8, 2006

Francois Gouget <fgouget(a)free.fr> writes: > On Tue, 7 Feb 2006, Huw D M Davies wrote: > [...] >> Why is WELSH in between TIBETAN and TIGRIGNA ? > > No idea. Must be a bug in the sort algorithm ;-) > Here's a corrected patch. ... > +#define LANG_YORUBA 0x6a > +#define LANG_WELSH 0x52 > +#define LANG_ZULU 0x35 The sort algorithm still needs some work ;-) On a more serious note, you'll need to fix the registry entries in wine.inf, otherwise the tests fail. -- Alexandre Julliard julliard(a)winehq.org

1 0

[dinput] dynamic handling of buttons of a device
by Christoph Frick Feb. 8, 2006

Feb. 8, 2006

attempt #2: this patch detects and maps the buttons dynamically instead of the hardcoded way it was before. this fixes the problems with devices, that report events in the joystick _and_ gamepad range of button events License: LGPL ChangeLog: 2006-02-08 Christoph Frick <rid(a)zefix.tv> - dlls/dinput/joystick_linuxinput.c dynamic assignment of buttons on a device -- cu Index: dlls/dinput/joystick_linuxinput.c =================================================================== RCS file: /home/wine/wine/dlls/dinput/joystick_linuxinput.c,v retrieving revision 1.35 diff -u -r1.35 joystick_linuxinput.c --- dlls/dinput/joystick_linuxinput.c 23 Nov 2005 19:29:19 -0000 1.35 +++ dlls/dinput/joystick_linuxinput.c 8 Feb 2006 12:22:53 -0000 @@ -120,7 +120,9 @@ int ff_state; /* data returned by the EVIOCGABS() ioctl */ - int axes[ABS_MAX+1][5]; + int axes[ABS_MAX][5]; + /* LUT for KEY_ to offset in rgbButtons */ + BYTE buttons[KEY_MAX]; #define AXE_ABS 0 #define AXE_ABSMIN 1 @@ -457,7 +459,7 @@ */ static HRESULT WINAPI JoystickAImpl_Acquire(LPDIRECTINPUTDEVICE8A iface) { - int i; + int i,buttons; JoystickImpl *This = (JoystickImpl *)iface; char buf[200]; BOOL readonly = TRUE; @@ -529,7 +531,7 @@ if (test_bit(This->absbits,i)) { if (-1==ioctl(This->joyfd,EVIOCGABS(i),&(This->axes[i]))) continue; - FIXME("axe %d: cur=%d, min=%d, max=%d, fuzz=%d, flat=%d\n", + TRACE("axe %d: cur=%d, min=%d, max=%d, fuzz=%d, flat=%d\n", i, This->axes[i][AXE_ABS], This->axes[i][AXE_ABSMIN], @@ -541,7 +543,14 @@ This->havemax[i] = This->axes[i][AXE_ABSMAX]; } } - MESSAGE("\n"); + buttons = 0; + for (i=0;i<KEY_MAX;i++) { + if (test_bit(This->keybits,i)) { + TRACE("button %d: %d\n", i, buttons); + This->buttons[i] = 0x80 | buttons; + buttons++; + } + } fake_current_js_state(This); @@ -661,6 +670,7 @@ struct timeval tv; fd_set readfds; struct input_event ie; + int btn; if (This->joyfd==-1) return; @@ -680,76 +690,14 @@ TRACE("input_event: type %d, code %d, value %d\n",ie.type,ie.code,ie.value); switch (ie.type) { case EV_KEY: /* button */ - switch (ie.code) { - case BTN_TRIGGER: /* normal flight stick */ - case BTN_A: /* gamepad */ - case BTN_1: /* generic */ - This->js.rgbButtons[0] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(0),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_THUMB: - case BTN_B: - case BTN_2: - This->js.rgbButtons[1] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(1),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_THUMB2: - case BTN_C: - case BTN_3: - This->js.rgbButtons[2] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(2),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_TOP: - case BTN_X: - case BTN_4: - This->js.rgbButtons[3] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(3),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_TOP2: - case BTN_Y: - case BTN_5: - This->js.rgbButtons[4] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(4),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_PINKIE: - case BTN_Z: - case BTN_6: - This->js.rgbButtons[5] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(5),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); + btn = This->buttons[ie.code]; + TRACE("(%p) %d -> %d\n", This, ie.code, btn); + if (btn&0x80) { + btn &= 0x7F; + This->js.rgbButtons[btn] = ie.value?0x80:0x00; + GEN_EVENT(DIJOFS_BUTTON(btn),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); + } break; - case BTN_BASE: - case BTN_TL: - case BTN_7: - This->js.rgbButtons[6] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(6),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_BASE2: - case BTN_TR: - case BTN_8: - This->js.rgbButtons[7] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(7),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_BASE3: - case BTN_TL2: - case BTN_9: - This->js.rgbButtons[8] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(8),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_BASE4: - case BTN_TR2: - This->js.rgbButtons[9] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(9),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - case BTN_BASE5: - case BTN_SELECT: - This->js.rgbButtons[10] = ie.value?0x80:0x00; - GEN_EVENT(DIJOFS_BUTTON(10),ie.value?0x80:0x0,ie.time.tv_usec,(This->dinput->evsequence)++); - break; - default: - FIXME("unhandled joystick button %x, value %d\n",ie.code,ie.value); - break; - } - break; case EV_ABS: switch (ie.code) { case ABS_X: @@ -794,6 +742,9 @@ This->ff_state = ie.value; break; #endif + case EV_SYN: + /* there is nothing to do */ + break; default: FIXME("joystick cannot handle type %d event (code %d)\n",ie.type,ie.code); break; @@ -1141,7 +1092,7 @@ if ((dwFlags == DIDFT_ALL) || (dwFlags & DIDFT_BUTTON)) { - int i; + int i, btncount=0; /*The DInput SDK says that GUID_Button is only for mouse buttons but well*/ @@ -1149,74 +1100,10 @@ for (i = 0; i < KEY_MAX; i++) { if (!test_bit(This->keybits,i)) continue; - - switch (i) { - case BTN_TRIGGER: - case BTN_A: - case BTN_1: - ddoi.dwOfs = DIJOFS_BUTTON(0); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 0) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_THUMB: - case BTN_B: - case BTN_2: - ddoi.dwOfs = DIJOFS_BUTTON(1); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 1) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_THUMB2: - case BTN_C: - case BTN_3: - ddoi.dwOfs = DIJOFS_BUTTON(2); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 2) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_TOP: - case BTN_X: - case BTN_4: - ddoi.dwOfs = DIJOFS_BUTTON(3); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 3) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_TOP2: - case BTN_Y: - case BTN_5: - ddoi.dwOfs = DIJOFS_BUTTON(4); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 4) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_PINKIE: - case BTN_Z: - case BTN_6: - ddoi.dwOfs = DIJOFS_BUTTON(5); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 5) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_BASE: - case BTN_TL: - case BTN_7: - ddoi.dwOfs = DIJOFS_BUTTON(6); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 6) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_BASE2: - case BTN_TR: - case BTN_8: - ddoi.dwOfs = DIJOFS_BUTTON(7); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 7) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_BASE3: - case BTN_TL2: - case BTN_9: - ddoi.dwOfs = DIJOFS_BUTTON(8); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 8) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_BASE4: - case BTN_TR2: - ddoi.dwOfs = DIJOFS_BUTTON(9); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 9) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - case BTN_BASE5: - case BTN_SELECT: - ddoi.dwOfs = DIJOFS_BUTTON(10); - ddoi.dwType = DIDFT_MAKEINSTANCE((0x0001 << 10) << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; - break; - } - sprintf(ddoi.tszName, "%d-Button", i); + ddoi.dwOfs = DIJOFS_BUTTON(btncount); + ddoi.dwType = DIDFT_MAKEINSTANCE(btncount << WINE_JOYSTICK_BUTTON_BASE) | DIDFT_PSHBUTTON; + sprintf(ddoi.tszName, "%d-Button", btncount); + btncount++; _dump_OBJECTINSTANCEA(&ddoi); if (lpCallback(&ddoi, lpvRef) != DIENUM_CONTINUE) { /* return to unaquired state if that's where we were */

1 0

[wined3d] better warn/fixme for query handling
by Christoph Frick Feb. 8, 2006

Feb. 8, 2006

hiho, this is one of three patches i still have in my cvs-tree that are not supplied. like the following i tired to submit several times - except for this one i never got a feedback, whats wrong. Licence: LGPL ChangeLog: 2006-02-08 Christoph Frick <rid(a)zefix.tv> - dlls/wined3d/device.c more granular handling of errors for queries -- cu Index: dlls/wined3d/device.c =================================================================== RCS file: /home/wine/wine/dlls/wined3d/device.c,v retrieving revision 1.125 diff -u -r1.125 device.c --- dlls/wined3d/device.c 7 Feb 2006 16:02:51 -0000 1.125 +++ dlls/wined3d/device.c 8 Feb 2006 12:23:00 -0000 @@ -1095,8 +1095,14 @@ if (NULL == ppQuery) { /* Just a check to see if we support this type of query */ HRESULT hr = D3DERR_NOTAVAILABLE; - /* Lie and say everything is good (we can return ok fake data from a stub) */ switch(Type) { + case WINED3DQUERYTYPE_OCCLUSION: + TRACE("(%p) occlusion query\n", This); + if (GL_SUPPORT(ARB_OCCLUSION_QUERY) || GL_SUPPORT(NV_OCCLUSION_QUERY)) + hr = D3D_OK; + else + WARN("Unsupported in local OpenGL implementation: ARB_OCCLUSION_QUERY/NV_OCCLUSION_QUERY\n"); + break; case WINED3DQUERYTYPE_VCACHE: case WINED3DQUERYTYPE_RESOURCEMANAGER: case WINED3DQUERYTYPE_VERTEXSTATS: @@ -1110,16 +1116,11 @@ case WINED3DQUERYTYPE_PIXELTIMINGS: case WINED3DQUERYTYPE_BANDWIDTHTIMINGS: case WINED3DQUERYTYPE_CACHEUTILIZATION: - break; - case WINED3DQUERYTYPE_OCCLUSION: - TRACE("(%p) occlusion query\n", This); - if (GL_SUPPORT(ARB_OCCLUSION_QUERY) || GL_SUPPORT(NV_OCCLUSION_QUERY)) - hr = D3D_OK; - break; + FIXME("(%p) Unsupported query type %d\n", This, Type); + break; default: - FIXME("(%p) Unhandled query type %d\n",This , Type); + FIXME("(%p) Unhandled query type %d\n", This, Type); } - FIXME("(%p) : Stub request for query type %d returned %ld\n", This, Type, hr); return hr; }

1 0

re: riched20 conformance test + find fix [bug 4479]
by Dan Kegel Feb. 7, 2006

Feb. 7, 2006

Thomas Kho wrote in http://www.winehq.org/pipermail/wine-patches/2006-February/023959.html : > ... fixes bug 4479 (find has a bounds bug). > Additionally, this patch adds a conformance test for rich edit with > tests for EM_FINDTEXT and EM_FINDTEXTEX. Tommy, your haystack[] variable is long and complex. Can you get the same testing out of a shorter sample string? Can you add a comment for each little check, translating it into english? All your tests seem to use the FR_MATCHCASE and FR_DOWN flags, could you also test without those flags a bit more? How sure are you about the bugfix? Are there other places in the source where a similar off-by-one error is made? Otherwise this looks great. - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

1 0