January 2005 - Wine-Devel - list.winehq.org

Re: another build problem on current cvs

by Vincent Béron

Le sam 01/01/2005 à 09:20, Andreas Mohr a écrit : [snip] > Problem is that we might want to have Wine never break during compile. > At least for semi-modern software versions it should compile successfully, > no matter how much functionality we have to disable to achieve that. Right. > > Configure check, anyone? To disable Alsa if alsa 0.9x headers are detected? I don't have either 0.9.x or 1.0 here, so I'd prefer somebody who has at least one of them to change configure.ac. Vincent

Jan. 3, 2005

Re: December 2004 - more patches than you can shake a stick at

by Joris Huizer

Rein Klazes wrote: > On Sun, 02 Jan 2005 14:57:27 +0000, you wrote: > > >>Being the patch fetishist that I am, I couldn't help noticing that in >>December 2004 we cleared 8mb of patches: that's by far the largest since >>the current archives began in October 2000. > > > For those that like such statistics: > > http://home.wanadoo.nl/wijn/wine/cvssize.png > > Rein. > > Am I the only one who thinks that trend line isn't up to date? :p

Jan. 2, 2005

Re: Approving of the WINEprobe initiative

by David Gümbel

On Dienstag 21 Dezember 2004 05:46, Brian Vincent wrote: > On Mon, 20 Dec 2004 19:13:00 +0100, David Gümbel > <david.guembel(a)itomig.de> wrote: > > Jep, its actually a pun: WINEprobe means be something like WINEtasting > > in english an maybe "degustation de WINE" in french. It's a little hard > > to translate puns, sorry ;) Maybe this is helpful: > > http://dict.leo.org/?search=weinprobe > So as far as official endorsement.. I'm sure someone in the Wine > community will speak up if they disagree with anything. (Conversely, > they won't speak up if they agree.) The three projects you mentioned > all sound great and they're things that really should be worked on. As the feedback has been IMO very positive (well, if we abstract over certain implications of the name of the initiative in english ;) and nobody came up with objections, I now consider it safe to say this initiative is being approved of by the Wine community. I wanted to thank everybody who provided feedback and comments. Plus, a happy new year to all of you! Bye, David

Jan. 2, 2005

Re: Debugging mingw applications using wine

by Eric Pouech

Dimitrie O. Paun a écrit : > On Sun, Jan 02, 2005 at 11:35:07AM +0100, Eric Pouech wrote: > >>winedbg using the gdb won't work here because (likely on unix) gdb isn't >>compiled with proper 'stabs in PE' support > > > Maybe we should lobby people (like Fedora) to enable it by default. > but this would require teaching gdb to use winelib too A+

Jan. 2, 2005

Re: spy.c in debug output

by Dimitrie O. Paun

On Sun, Jan 02, 2005 at 04:47:41PM +0000, Mike Hearn wrote: > Perhaps we could provide a Wine specific API and then an inline > function that does a GetProcAddress on it, and if it's missing just passes > the number straight through. Right. A default implementation could be just: wine_dbg_sprintf("%x", msg); Anyway, it would be way cool if we could use the nice dumping functions from spy. We should be exporting a wine_dbg_msg_{enter,exit}() that we could use them nicely in our window procs. In fact, I don't think it's feasible to return a string (the max buffer is probably not big enough), we should just dump the output automagically to the correct channel, so maybe a better name would be: wine_dbg_msg_{enter,exit}_dump() Hmm, it needs a bit more thought, we also need a calling macro to hide the channel business: TRACE_MSG_ENTER()/TRACE_MSG_EXIT() -- Dimi.

Jan. 2, 2005

Re: spy.c in debug output

by Dimitrie O. Paun

On Sun, Jan 02, 2005 at 05:22:43PM +0100, Eric Pouech wrote: > because they are not exported as regular APIs from user32, and we must > stick to what the Win32 API provides for inter DLL calls True, but they are useful. Maybe we can move them to libwine, or do a trick of sorts with GetProcAddress(). -- Dimi.

Jan. 2, 2005

Re: Debugging mingw applications using wine

by Dimitrie O. Paun

On Sun, Jan 02, 2005 at 11:35:07AM +0100, Eric Pouech wrote: > winedbg using the gdb won't work here because (likely on unix) gdb isn't > compiled with proper 'stabs in PE' support Maybe we should lobby people (like Fedora) to enable it by default. -- Dimi.

Jan. 2, 2005

Re: spy.c in debug output

by Mike Hearn

On Sun, 02 Jan 2005 17:22:43 +0100, Eric Pouech wrote: > because they are not exported as regular APIs from user32, and we must stick to > what the Win32 API provides for inter DLL calls Perhaps we could provide a Wine specific API and then an inline function that does a GetProcAddress on it, and if it's missing just passes the number straight through. That way there are no hard dependencies between the DLLs but when run using Wine user32 the traces are more helpful. Thoughts? thanks -mike

Jan. 2, 2005

Re: December 2004 - more patches than you can shake a stick at

by Mike Hearn

On Sun, 2005-01-02 at 17:07 +0100, Maxime Bellengé wrote: > Happy new year everybody ! > > In your list, you forgot your big work on systray. Do you see in your > crystal ball if/when it will be merged ? We'll see ;) Every so often I do a sprint on that patch, and each time it gets a bit closer to what Alexandre wants. The main problem is that I don't actually know what his vision for this code is, he never spells it out. So each time I improve it a few times but it's still not good enough, and I get bored/frustrated and move onto something else. I'll probably return to it in a few months. If somebody else wants to run with it of course they are welcome to do so. thanks -mike

Jan. 2, 2005

Re: December 2004 - more patches than you can shake a stick at

by Rein Klazes

On Sun, 02 Jan 2005 14:57:27 +0000, you wrote: > Being the patch fetishist that I am, I couldn't help noticing that in > December 2004 we cleared 8mb of patches: that's by far the largest since > the current archives began in October 2000. For those that like such statistics: http://home.wanadoo.nl/wijn/wine/cvssize.png Rein.

Jan. 2, 2005