Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
Martin Simmons
martin at lispworks.com
Thu Jan 12 14:38:29 UTC 2012
>>>>> On Wed, 11 Jan 2012 11:47:40 -0600, Chuck Burns said:
>
> On 01/11/12 10:24, Martin Simmons wrote:
> >>>>>> 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
> > _______________________________________________
> > freebsd-emulation at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe at freebsd.org"
> wow64 doesnt -exist- in wine64 unless you compile the 32bit wine
> alongside it.
>
> You have to build it twice, to get two binaries "wine" and "wine64" and
> if you build them "properly" what happens when you attempt to execute a
> 64bit app with "wine" it's automatically relaunched with "wine64" But
> the reverse is NOT true.
OK, that's what I would call unstable. Eventually though, I would expect a
packaged wine64 to include wow64, just like Windows does.
__Martin
More information about the freebsd-emulation
mailing list