December 2008 - Wine-Devel - list.winehq.org

d3d9/visual tests timed out
by Rico Schüller Dec. 24, 2008

Dec. 24, 2008

Hi, on my XP machine the visual d3d9 test produces a timeout message, when it is started from the winetest build. Anyone here could run the tests on windows without a timeout (and off course without skipping half of the tests - have to be more than 4k tests)? Also there is no message about a timeout on the test site ( http://test.winehq.org/data/028617b90ba586bdb30723c700eea888c159ada7/xp_rs-… ). Cheers Rico

4 4

Re: oledlg: Implement OleUIAddVerbMenuA/W functions [resend]
by Vitaly Lipatov Dec. 24, 2008

Dec. 24, 2008

Hello, Can anyone comment what bad with my OleUIAddVerbMenuA/W implementation. I know no one is interested in this function at your side, but it is really used function for more than one year. В сообщении от 20 декабря 2008 Vitaly Lipatov написал(a): > Real implementation of the OleUIAddVerbMenu function. -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

2 1

Re: Testing DIB Engine (second part)
by Paul Vriens Dec. 24, 2008

Dec. 24, 2008

Massimo Del Fedele wrote: > Here the second part, it contains winedib.drv code and changes to > Makefiles. > > Still no way to enable/disable the engine, besides of deleting the .so > inside dlls/winedib.drv. > > I'll wait for some feedback before going fourther. > > Ciao > > Max > > > ------------------------------------------------------------------------ > > Hi Max I don't think this should have gone to wine-patches but to wine-devel instead. After all it's a proof of concept and not a complete solution. Could you also zip these huge things up in the future (mail is now 1217KB)? -- Cheers, Paul.

3 3

Regression: Sound broken in PoP series
by M.Kiesel Dec. 24, 2008

Dec. 24, 2008

Hi! The following commit breaks sound in (at least) Prince of Persia SoT and PoP TWW. Reece, let me know how I can help with that. commit ce06de420874b9983324508f8257a580fee341ca Author: Reece Dunn <msclrhd(a)googlemail.com> Date: Mon Dec 22 13:33:43 2008 +0000 dsound: Correct the dsound fraglen calculations. Regards

2 1

Re: [Wine] Re: MacOS X cocoa and carbon for Linux?
by James McKenzie Dec. 24, 2008

Dec. 24, 2008

Richie wrote: > James McKenzie wrote: > >> hahomir4ev wrote: >> You might find a friendly discussion somewhere else on the >> implementation of Cocoa/Carbon on Linux, but this is not a topic of >> discussion here. >> James McKenzie >> > > Of cource it would be a completely unrelated project. Therefore the wine forum is not the right place for such a project. > BUT: Up to now there is no McWine or MINE project. Sad to say, but there IS a project for porting Wine to the PowerPC platform: Darwine. It has stalled and really could use help. It has forked so that there are two paths of development and the Intel fork is being worked back into the main Wine project. That leaves the PowerPC fork to be worked on to incorporate Qemu, an x86 emulator for the PowerPC. As to the Aqua 'look and feel' there is an effort to do this as well that may or may not need assistance. The goal in that project is to remove all Object C code and replace it with 'c' code equivalents. You can ask the status of that project on the Wine Development list. Again, this is not the area for discussing development of Wine. Let's move this to the appropriate venue. Thank you. James McKenzie

1 0

re: Symlink vulnerability in winetricks
by Dan Kegel Dec. 24, 2008

Dec. 24, 2008

Stefan Nordhaus wrote: > Winetricks has a symlink vulnerability... Fixed in today's winetricks (20081223), thanks! - Dan

1 0

Trouble compiling today's git.
by Susan Cragin Dec. 24, 2008

Dec. 24, 2008

Is anyone else having trouble compiling today's git? Or is it just my flu-addled brain? make[1]: Entering directory `/home/susan/wine/server' ../tools/makedep -C. -S.. -T.. async.c atom.c change.c class.c clipboard.c completion.c console.c context_alpha.c context_i386.c context_powerpc.c context_sparc.c context_x86_64.c debugger.c device.c directory.c event.c fd.c file.c handle.c hook.c mach.c mailslot.c main.c mapping.c mutex.c named_pipe.c object.c process.c procfs.c ptrace.c queue.c region.c registry.c request.c semaphore.c serial.c signal.c snapshot.c sock.c symlink.c thread.c timer.c token.c trace.c unicode.c user.c window.c winstation.c make[1]: Leaving directory `/home/susan/wine/server' make[1]: Entering directory `/home/susan/wine/server' ../tools/makedep -C. -S.. -T.. async.c atom.c change.c class.c clipboard.c completion.c console.c context_alpha.c context_i386.c context_powerpc.c context_sparc.c context_x86_64.c debugger.c device.c directory.c event.c fd.c file.c handle.c hook.c mach.c mailslot.c main.c mapping.c mutex.c named_pipe.c object.c process.c procfs.c ptrace.c queue.c region.c registry.c request.c semaphore.c serial.c signal.c snapshot.c sock.c symlink.c thread.c timer.c token.c trace.c unicode.c user.c window.c winstation.c make[1]: Leaving directory `/home/susan/wine/server' make[1]: Entering directory `/home/susan/wine/tools' make[2]: Entering directory `/home/susan/wine/tools/widl' ../../tools/makedep -C. -S../.. -T../.. client.c expr.c hash.c header.c proxy.c server.c typegen.c typelib.c utils.c widl.c write_msft.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/widl' make[2]: Entering directory `/home/susan/wine/tools/widl' ../../tools/makedep -C. -S../.. -T../.. client.c expr.c hash.c header.c proxy.c server.c typegen.c typelib.c utils.c widl.c write_msft.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/widl' make[2]: Entering directory `/home/susan/wine/tools/winebuild' ../../tools/makedep -C. -S../.. -T../.. import.c main.c parser.c relay.c res16.c res32.c spec16.c spec32.c utils.c make[2]: Leaving directory `/home/susan/wine/tools/winebuild' make[2]: Entering directory `/home/susan/wine/tools/winebuild' ../../tools/makedep -C. -S../.. -T../.. import.c main.c parser.c relay.c res16.c res32.c spec16.c spec32.c utils.c make[2]: Leaving directory `/home/susan/wine/tools/winebuild' make[2]: Entering directory `/home/susan/wine/tools/winedump' ../../tools/makedep -C. -S../.. -T../.. debug.c dos.c dump.c emf.c le.c lib.c lnk.c main.c minidump.c misc.c msc.c msmangle.c ne.c output.c pdb.c pe.c search.c symbol.c make[2]: Leaving directory `/home/susan/wine/tools/winedump' make[2]: Entering directory `/home/susan/wine/tools/winedump' ../../tools/makedep -C. -S../.. -T../.. debug.c dos.c dump.c emf.c le.c lib.c lnk.c main.c minidump.c misc.c msc.c msmangle.c ne.c output.c pdb.c pe.c search.c symbol.c make[2]: Leaving directory `/home/susan/wine/tools/winedump' make[2]: Entering directory `/home/susan/wine/tools/winegcc' ../../tools/makedep -C. -S../.. -T../.. utils.c winegcc.c make[2]: Leaving directory `/home/susan/wine/tools/winegcc' make[2]: Entering directory `/home/susan/wine/tools/winegcc' ../../tools/makedep -C. -S../.. -T../.. utils.c winegcc.c make[2]: Leaving directory `/home/susan/wine/tools/winegcc' make[2]: Entering directory `/home/susan/wine/tools/wmc' ../../tools/makedep -C. -S../.. -T../.. lang.c mcl.c utils.c wmc.c write.c mcy.y make[2]: Leaving directory `/home/susan/wine/tools/wmc' make[2]: Entering directory `/home/susan/wine/tools/wmc' ../../tools/makedep -C. -S../.. -T../.. lang.c mcl.c utils.c wmc.c write.c mcy.y make[2]: Leaving directory `/home/susan/wine/tools/wmc' make[2]: Entering directory `/home/susan/wine/tools/wrc' ../../tools/makedep -C. -S../.. -T../.. dumpres.c genres.c newstruc.c readres.c translation.c utils.c wrc.c writeres.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/wrc' make[2]: Entering directory `/home/susan/wine/tools/wrc' ../../tools/makedep -C. -S../.. -T../.. dumpres.c genres.c newstruc.c readres.c translation.c utils.c wrc.c writeres.c parser.y parser.l make[2]: Leaving directory `/home/susan/wine/tools/wrc' ../tools/makedep -C. -S.. -T.. -I/usr/include/freetype2 fnt2bdf.c fnt2fon.c make_ctests.c makedep.c relpath.c sfnt2fnt.c make[1]: Leaving directory `/home/susan/wine/tools' ./tools/makedep -C. -S. -T. make[1]: Entering directory `/home/susan/wine/tools' make[1]: `makedep' is up to date. make[1]: Leaving directory `/home/susan/wine/tools' make[1]: Entering directory `/home/susan/wine/libs' make[2]: Entering directory `/home/susan/wine/libs/port' ../../tools/widl/widl -I. -I. -I../../include -I../../include -D__WINESRC__ -h -H ../../include/wtypes.h ../../include/wtypes.idl make[2]: ../../tools/widl/widl: Command not found make[2]: *** [../../include/wtypes.h] Error 127 make[2]: Leaving directory `/home/susan/wine/libs/port' make[1]: *** [port] Error 2 make[1]: Leaving directory `/home/susan/wine/libs' make: *** [libs] Error 2 susan(a)ubuntu:~/wine$

2 1

Re: [06/10] wintrust: Implement CryptCATOpen and CryptCATClose.
by Maarten Lankhorst Dec. 23, 2008

Dec. 23, 2008

Hi Juan and Hans, Juan Lang schreef: > Hi Hans, > > >> Maarten, do you remember what the code to store attribute certs was >> needed for? I'd like to address Juan's concern by either adding a test >> or taking the code out. >> > > I wouldn't worry about it. The code looks correct to the eye, it's > just calling part of crypt32 that's stubbed out (and on my list.) > Mainly I was curious if you'd managed to test with native crypt32 > somehow, as that's something I've never managed to make work (on > Linux.) > I was working on some code that needed it, The specific functions were stubbed out (crossover proprietary advantage (TM)) so it's not used, but the correct implementation of CryptCATGetCertAttr/CryptCATEnumCertAttr would need the attributes. Cheers, Maarten.

1 0

how to create a broken .tlb file
by Michael Karcher Dec. 23, 2008

Dec. 23, 2008

Hello developers, while debugging problems with and old version of Sonic Stage, I found that sonic stage includes broken type libraries, i.e. the TYPEFLAG_FDISPATCHABLE bit is generally missing. As widl (and probably midl too) set this bit automatically, I have some problems in creating a .tlb file for a test case for my one-line patch that also misses this bit. There are some possibilities to get around the problem: a) Include a broken (hand-patched) tlb file as binary file in git b) Include a program that breaks tlb files and call it while building tests c) Include tlb file patching into the testcase (i.e. copy a good tlb, patch it, and perform some tests with the copy, than delete it) Which approach would have the highest chance of getting the fix (including the testcase that tests broken type libraries) included into Wine? Regards, Michael Karcher

2 1

Re: bugfix: resend: fix serial_flush
by Alexandre Julliard Dec. 23, 2008

Dec. 23, 2008

Wolfgang Walter <wine(a)stwm.de> writes: > @@ -201,7 +202,17 @@ static void serial_flush( struct fd *fd, struct event **event ) > /* MSDN says: If hFile is a handle to a communications device, > * the function only flushes the transmit buffer. > */ > - if (tcflush( get_unix_fd(fd), TCOFLUSH ) == -1) file_set_error(); > + /* FlushFileBuffers does NOT have the semantics of tcflush. > + * Whereas tcflush discards any data not yet transmitted > + * FlushFileBuffers ensures they are written out. > + * The POSIX equivalent is tcdrain > + */ > + while (tcdrain( get_unix_fd(fd)) == -1) { > + if (errno != EINTR) { > + file_set_error(); > + return; > + } This will block, you can't do that in the server. -- Alexandre Julliard julliard(a)winehq.org

2 2

Symlink vulnerability in winetricks
by Stefan Nordhausen Dec. 23, 2008

Dec. 23, 2008

Hi! Winetricks has a symlink vulnerability, it does (echo "$title"; echo ""; echo "$text") > /tmp/x_showmenu.txt An attacker can exploit this by creating a symlink called /tmp/x_showmenu.txt and have it point to some file that a winetricks user can write (e.g. ~/Documents/important_stuff.odf). Winetricks will then overwrite that file with its data. To solve this, apply the following patch that simply avoids the creation of a temporary file: --- winetricks 2008-12-18 06:34:42.000000000 +0100 +++ winetricks 2008-12-23 18:00:17.000000000 +0100 @@ -207,8 +207,8 @@ args="$args,$1" shift done - (echo "$title"; echo ""; echo "$text") > /tmp/x_showmenu.txt - xmessage -print -file /tmp/x_showmenu.txt -buttons "Cancel,$args" | sed 's/Cancel//' + (echo "$title"; echo ""; echo "$text") | \ + xmessage -print -file - -buttons "Cancel,$args" | sed 's/Cancel//' } showmenu() Merry Christmas Stefan

1 0

DIB Engine
by Massimo Del Fedele Dec. 23, 2008

Dec. 23, 2008

As my DIB engine is becoming usable (I already use it on Autocad for my job), I'm thinking to publish the patches. As it's still not complete, I'm thinking to add a way to enable it on demand with registry and environment variable : export WINEDIB=ON activates it export WINEDIB=OFF deactivates it if no environment variable, it checks a registry key (I'd like to have some suggestion on where to put it). If no environment variable nor registry entry are present it'll be disabled (by now) as is for testing purposes. How should I publish it ? A big unique patch, 2 patches, one with the (small) changes in gdi32 and another big one with the engine itself, or many small patches ? Is it right to put on wine patches list ? Ciao Max

5 6

RE: d3d9/tests: Don't create a Null-shader in d3d9, it will crash.
by Stefan Dösinger Dec. 23, 2008

Dec. 23, 2008

I never saw this crashing on any of my systems, so it is probably driver dependent. Which Windows driver are you using? If the test crashes on either ATI, Nvidia or Intel it is a good idea to remove it. I don't think we should remove it if it crashes on something like VMWare or other 'noname' cards.

4 4

MSVCP80 implementation
by louis＠museresearch.com Dec. 23, 2008

Dec. 23, 2008

Hi all, I'm attempting to get software to run which requires some functions in MSVCP80 to be implemented. Using the original DLLs is not an option for us. In particular, a couple of the allocator functions are being called (msvcp80.dll.??0?$basic_string(a)DU?$char_traits(a)D@std@@V?$allocator(a)D@2@@std@@QAE(a)XZ to give one such example). I am sure there are more after this is fixed too. Browsing the WINE source, I found references to some similarly mangled functions in MSVCRT (the stream classes), but they did not seem to be actually implemented: in msvcrt/tests/cpp.c there was a demangling test, but I didn't find much else that was directly related. So, my question is how WINE handles calls to any STL or C++ library functions which may be included in these DLLs, and what approach I should use to implement or forward calls to these kinds of functions. Any help would be much appreciated. Thanks in advance, Louis Gorenfeld Muse Research

6 5

RE: d3d9: Set IDirect3DDevice9Impl_GetVertexShader return value to NULL on error
by Stefan Dösinger Dec. 23, 2008

Dec. 23, 2008

Hi, Please write a test for this. This behavior differs from function to function unfortunately. Some functions do not set the value to NULL, and some apps depend on this. I think dlls/d3d9/tests/shader.c is a good place to put this test. -----Original Message----- > From: wine-patches-bounces(a)winehq.org [mailto:wine-patches- > bounces(a)winehq.org] On Behalf Of Vincent Pelletier > Sent: Monday, December 22, 2008 11:25 PM > To: wine-patches > Subject: d3d9: Set IDirect3DDevice9Impl_GetVertexShader return value to > NULL on error > > When IWineD3DDevice_GetVertexShader fails, set *ppShader to NULL. > > This fixes "Black & White 2" here: it used to crash right when first > level intro video ended, before seeing the level. With this patch I can > play a bit (though there are some graphical glitches remaining, mouse > it not so > smooth...) > > -- > Vincent Pelletier

2 2

Valgrind warning in wined3d/swapchain.c in IWineD3DSwapChainImpl_Destroy
by Dan Kegel Dec. 23, 2008

Dec. 23, 2008

Hi Stefan, you seem to have been in this code recently, could you have a look? This is a somewhat flaky error that happens about 80% of the time under heavy load on my quad core box. (This is valgrind's xml output format, it's pretty fluffy, sorry.) Thanks, Dan <error> <kind>UninitCondition</kind> <what>Conditional jump or move depends on uninitialised value(s)</what> <stack> <frame> <obj>dlls/wined3d/wined3d.dll.so</obj> <fn>IWineD3DSwapChainImpl_Destroy</fn> <dir>dlls/wined3d</dir> <file>swapchain.c</file> <line>75</line> </frame> <frame> <obj>dlls/d3d9/d3d9.dll.so</obj> <fn>IDirect3DSwapChain9Impl_Release</fn> <dir>dlls/d3d9</dir> <file>swapchain.c</file> <line>66</line> </frame> <frame> <obj>dlls/d3d9/d3d9.dll.so</obj> <fn>D3D9CB_DestroySwapChain</fn> <dir>dlls/d3d9</dir> <file>directx.c</file> <line>427</line> </frame> <frame> <obj>dlls/wined3d/wined3d.dll.so</obj> <fn>IWineD3DDeviceImpl_Uninit3D</fn> <dir>dlls/wined3d</dir> <file>device.c</file> <line>2426</line> </frame> <frame> <obj>dlls/d3d9/d3d9.dll.so</obj> <fn>IDirect3DDevice9Impl_Release</fn> <dir>dlls/d3d9</dir> <file>device.c</file> <line>98</line> </frame> <frame> <obj>dlls/d3d9/tests/d3d9_test.exe.so</obj> <fn>func_visual</fn> <dir>dlls/d3d9/tests</dir> <file>visual.c</file> <line>9960</line> </frame> <frame> <obj>dlls/d3d9/tests/d3d9_test.exe.so</obj> <fn>run_test</fn> <dir>dlls/d3d9/tests/../../../include/wine</dir> <file>test.h</file> <line>452</line> </frame> <frame> <obj>dlls/d3d9/tests/d3d9_test.exe.so</obj> <fn>main</fn> <dir>dlls/d3d9/tests/../../../include/wine</dir> <file>test.h</file> <line>502</line> </frame> </stack> </error>

2 1

Re: winecfg: Disable nonfunctional advanced drive settings
by Austin English Dec. 23, 2008

Dec. 23, 2008

On Tue, Dec 23, 2008 at 2:36 AM, M.Kiesel <wine-devel(a)continuity.cjb.net> wrote: > In the winecfg drive tab, advanced drive settings (setting label and serial) > seem to be broken currently due to other Wine bugs (see drive.c > apply_drive_changes comments). Disable these settings for now since this > only confuses users. > > Changelog: > winecfg: Disable nonfunctional advanced drive settings > > > Rather than disable it and cause more confusion when it does work, focus on fixing the actual bug instead. -- -Austin

2 2

Re: Wine build failed
by Dmitry Timoshkov Dec. 23, 2008

Dec. 23, 2008

"Dmitry Timoshkov" <dmitry(a)codeweavers.com> wrote: >> building current git tree fails to me on Debian Etch (x86) with: >> >> ccache gcc -c -I../../../wine-git/dlls/gdi32 -I. -I../../../wine-git/include >> -I../../include -I/usr/include/freetype2 -D__WINESRC__ -D_GDI32_ >> -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing >> -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o >> font.o ../../../wine-git/dlls/gdi32/font.c ccache gcc -c >> -I../../../wine-git/dlls/gdi32 -I. -I../../../wine-git/include >> -I../../include -I/usr/include/freetype2 -D__WINESRC__ -D_GDI32_ >> -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing >> -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o >> freetype.o ../../../wine-git/dlls/gdi32/freetype.c >> ../../../wine-git/dlls/gdi32/freetype.c:187: error: expected declaration >> specifiers or ‘...’ before ‘FT_LcdFilter’ > > Remove a broken patch from your sources, that's not a "current git tree". I'm sorry, that patch is really in current git. -- Dmitry.

1 0

Re: cryptui(0/24)
by James McKenzie Dec. 23, 2008

Dec. 23, 2008

Juan Lang wrote: > This patch series implements the remaining portions of > CryptUIWizImport, and calls it from the certificate dialog. > > If all of this is accepted, this is one lengthy and needed functional implementation. Good job, Juan! James McKenzie

2 1

Re: MSVCP80 implementation
by James Mckenzie Dec. 23, 2008

Dec. 23, 2008

>"James McKenzie" <jjmckenzie51(a)earthlink.net> wrote: > >>>> I'm attempting to get software to run which requires some functions in >>>> MSVCP80 to be implemented. >>>> >>> You need to install msvc2005 redistributable runtime. The simplest way is >>> using winetricks: http://wiki.winehq.org/winetricks >>> >>> Implementing all that is a huge waste of time. >>> >>> >> Legally speaking, we should start implementing all of the functions in >> the Win32/Win64 API. > >MSVCP80 is not a part of win32 API, that's a redistributable run-time >library supposed to be provided by an application. > Dimtry: Thank you for the clarification on its use and where it should come from. I will correct then: Get it through Winetricks or insure that it is packaged with the executable. James McKenzie

1 0

Patchwatcher offline?
by IneedAname Dec. 23, 2008

Dec. 23, 2008

Looks like Patchwatcher has being offline from 09-Dec-2008. Did I miss something or did someone trip over the mains cable?

5 5

Re: [RFC] wined3d: Avoid triggering OPENGL errors when setting point size
by Henri Verbeet Dec. 23, 2008

Dec. 23, 2008

2008/12/23 Vincent Pelletier <plr.vincent(a)gmail.com>: > If WINED3DRS_POINTSCALEENABLE is false and WINED3DRS_POINTSIZE render state is > set to an invalid size, glPointSize will fail. > This happens in "Black & White 2", causing log/stderr to be flooded with > opengl errors. > > I'm not sure if this should be fixed here, or when setting state value. > Also, maybe it should be avoided to double-check against opengl bounds when > WINED3DRS_POINTSCALEENABLE is true. > I think it makes more sense to clamp the value to be within the limits, rather than using whatever was used last.

1 0

Fwd: Linking to a Mac OS X build of Wine from winehq.org/download ?
by Zach Drayer Dec. 22, 2008

Dec. 22, 2008

Begin forwarded message: > From: "Austin English" <austinenglish(a)gmail.com> > Date: December 22, 2008 6:12:13 PM EST > To: "Zach Drayer" <zach(a)drayer.name> > Subject: Re: Linking to a Mac OS X build of Wine from winehq.org/ > download ? > > On Mon, Dec 22, 2008 at 5:06 PM, Zach Drayer <zach(a)drayer.name> wrote: >> >> On Dec 22, 2008, at 10:25 AM, Austin English wrote: >>> >>> It currently has a few 'OS X-isms'. The patch that causes 100% cpu >>> usage on SSL sites in IE6 is reverted, as well as a few x11 hacks. >>> The >>> other main problem is fonts. >>> >>> I think we need to fix the X11 hacks needed before doing considering >>> it 'official' wine. We don't want a flood of bug reports for that >>> problem. >>> >> The big problem is that OS X's X11 still ships with libGL 1.2 >> while, iirc, >> wine requires libGL 1.3. I *believe* (but dont quote me on this) >> that Mike >> patches wine to remove this check. >> >>> What I would like to see is the changes made by Zach and Mike >>> incorporated >>> back into the main Wine code. >> >> I don't make any changes to wine; I just build bland wine and stick >> it in a >> .bundle application. >> >> On Dec 22, 2008, at 10:39 AM, James Mckenzie wrote: >>> >>> Both Mike and Zach have approached building Wine releases in the two >>> structures supported by Apple: Drag and Drop where you grab a pre- >>> built >>> Application object and move it into the Applications folder and >>> the use of >>> the Apple installer with an installable 'package' much like the >>> use of apt >>> or yum. There is great debate as to which is the best approach >>> and, basing >>> this on the struggle within and outside of the OpenOffice.org/ >>> NeoOffice.org >>> MacOSX porting projects, I would like to avoid this problem as >>> best we can. >>> Firefox and Thunderbird use the first approach, but many projects >>> use the >>> latter. >> >> Mike's builds work with drag and drop because he builds all the >> libraries >> that Darwine requires and sticks them in the bundle. >> >> The builds that I create rely on system libraries whenever >> possible. The >> reason my builds have an installer is because the system doesn't >> come with >> versions of FreeType or FontForge that are reasonably up to date. >> >> One notable difference here is that since Mike puts all his builds >> into the >> bundle, It has more compatibility (his versions support Tiger and >> Leopard, >> mine only works on Leopard). However, it comes at the cost of some >> features >> working (iirc, libcups works with my builds, but not his). >> >> -Zach >> > > I think you meant to send this to wine-devel as well. > Yup, sorry about that. Was about to forward it to the right place when i your email.

1 0

New Gecko package - call for tests
by Jacek Caban Dec. 22, 2008

Dec. 22, 2008

Hi, I've released first (and hopefully last) RC build of new Gecko package and attached a patch against current Wine Git to bug 16198 http://bugs.winehq.org/show_bug.cgi?id=16198 It's critical to make sure, that there will be no regressions due to the new Gecko, it'd much more work to fix such regression than a usual regressions. I'd appreciate any help with testing it. Instructions how to do it are in the bug report. Any application that uses MSHTML is worth testing, esp ones that extensively use it. I will write more about the new release and future plans later in an other subject. Thanks, Jacek

2 2

Re: ntdll: fix a compiler warning on PC-BSD
by Francois Gouget Dec. 22, 2008

Dec. 22, 2008

I'm a bit surprised that PC-BSD/FreeBSD's mkdir() does not take a mode argument. Are you sure this is really the case? Maybe we are just mising a #include directive on BSD? (Unfortunately I don't really have access to a FreeBSD box right now) -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ You can have my guns when you pry them from my kids cold, dead hands.

2 1