Date: Wed, 11 Jan 2012 16:24:21 GMT From: Martin Simmons <martin@lispworks.com> To: freebsd-emulation@freebsd.org Subject: Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD) Message-ID: <201201111624.q0BGOLlk030092@higson.cam.lispworks.com> In-Reply-To: <4F0CC7A4.4010707@gmail.com> (message from Chuck Burns on Tue, 10 Jan 2012 17:20:04 -0600) References: <201201092017.19776.naylor.b.david@gmail.com> <4F0B2FC4.7090002@gmail.com> <201201101849.29845.naylor.b.david@gmail.com> <4F0CC7A4.4010707@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Tue, 10 Jan 2012 17:20:04 -0600, Chuck Burns said: > > On 01/10/12 10:49, David Naylor wrote: > > I wasn't aware of WoW64 (and how it will make my packages redundent :->). I > > see there are two wiki pages: > > + http://wiki.winehq.org/Wine64 > > + http://wiki.winehq.org/Wine64ForPackagers > > > > The latter makes this statement "Wine 64bit works at the moment only on > > Linux." which would indicate that, at this stage, FreeBSD is precluded. That, > > however, is just my speculation. > > > > To answer your question directly, I have put no thought or effort into wine64. > > There is still a need for the 32bit wine, as the wow64 build will ONLY > run 64bit windows apps, so for the majority of applications and games, > we'll still need the 32bit wine. Is that because wow64 is unstable in wine64? Wow64's reason for existence is to run 32-bit Windows binaries on 64-bit Windows/Wine and it works pretty well for most applications. __Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201111624.q0BGOLlk030092>