Announcing the Mac driver
Greetings Wine community, As many of you may be aware, CodeWeavers just released CrossOver 12. We're pleased to announce that CrossOver 12 includes the long-awaited Mac driver. If you're not familiar with it, the Mac driver is an alternative to Wine's X11 driver for use on Mac OS X. It allows Wine to present windows, receive input from the keyboard and mouse, and interact with system facilities like the clipboard using Cocoa and other Mac-native APIs. That allows for superior integration into the Mac UI and eliminates the need for the foreign X11 middleware. The Mac driver is not yet complete but it's pretty far along. In CrossOver 12, it's described as an "experimental" feature and is disabled by default. We're aware of chunks of functionality, both big and small, that are simply not implemented yet and there are surely many bugs in need of squashing. You can take a look at the source in CodeWeavers' usual Wine source tarball at <http://www.codeweavers.com/products/faq/source/>. The Mac driver lives in dlls/winemac.drv. Because it was under (somewhat chaotic) development right up until the release of CrossOver 12, we do not yet have a series of clean patches for it to submit to Wine. In the coming days and weeks, I will be reconstructing the Mac driver as just such a patch series and submitting it. Mind you, those patches will face the same demanding scrutiny from Alexandre as everything else, so that process may be slow and painful. I'm SO looking forward to that! Thank you to everyone who contributes to Wine for making this possible. It will be fun to work with you on continuing development of the Mac driver. Cheers, Ken
--- On Wed, 12/12/12, Ken Thomases <ken(a)codeweavers.com> wrote:
Greetings Wine community,
As many of you may be aware, CodeWeavers just released CrossOver 12. We're pleased to announce that CrossOver 12 includes the long-awaited Mac driver. If you're not familiar with it, the Mac driver is an alternative to Wine's X11 driver for use on Mac OS X. It allows Wine to present windows, receive input from the keyboard and mouse, and interact with system facilities like the clipboard using Cocoa and other Mac-native APIs. That allows for superior integration into the Mac UI and eliminates the need for the foreign X11 middleware.
The Mac driver is not yet complete but it's pretty far along. In CrossOver 12, it's described as an "experimental" feature and is disabled by default. We're aware of chunks of functionality, both big and small, that are simply not implemented yet and there are surely many bugs in need of squashing.
You can take a look at the source in CodeWeavers' usual Wine source tarball at <http://www.codeweavers.com/products/faq/source/>. The Mac driver lives in dlls/winemac.drv. Because it was under (somewhat chaotic) development right up until the release of CrossOver 12, we do not yet have a series of clean patches for it to submit to Wine. In the coming days and weeks, I will be reconstructing the Mac driver as just such a patch series and submitting it. Mind you, those patches will face the same demanding scrutiny from Alexandre as everything else, so that process may be slow and painful. I'm SO looking forward to that!
:-).
Thank you to everyone who contributes to Wine for making this possible. It will be fun to work with you on continuing development of the Mac driver.
Cheers, Ken
Well-done for the work and cheers. I am somewhat curious about the tar ball - why is the version 12 source (120MB) and so much bigger than the previous (44MB)? I can probably work it out by downloading and unpacking both, but I am feeling lazy... Hin-Tak
--- On Wed, 12/12/12, Josh DuBois <duboisj(a)codeweavers.com> wrote:
wine-mono.
On 12/12/12 4:27 PM, Hin-Tak Leung wrote:
I am somewhat curious about the tar ball - why is the version 12 source (120MB) and so much bigger than the previous (44MB)? I can probably work it out by downloading and unpacking both, but I am feeling lazy... Hin-Tak
Thank you. That makes sense - that's the size of mono thereabouts. I guess my next question is, does it also have codeweaver-specific bits? Sorry this sounds rather lazy, but I am sure more than one person wants to know :-). Hin-Tak
Am 12.12.2012 23:35, schrieb Hin-Tak Leung:
--- On Wed, 12/12/12, Josh DuBois <duboisj(a)codeweavers.com> wrote:
wine-mono.
On 12/12/12 4:27 PM, Hin-Tak Leung wrote:
I am somewhat curious about the tar ball - why is the version 12 source (120MB) and so much bigger than the previous (44MB)? I can probably work it out by downloading and unpacking both, but I am feeling lazy... Hin-Tak
Thank you. That makes sense - that's the size of mono thereabouts. I guess my next question is, does it also have codeweaver-specific bits? Sorry this sounds rather lazy, but I am sure more than one person wants to know :-).
I bet it has as things without change like wine-gecko are not included. the problem is without a clean wine-mono checkout it's hard to see what changed, a folder with patches in addition would be great. -- Best Regards, André Hentschel
--- On Wed, 12/12/12, André Hentschel <nerv(a)dawncrow.de> wrote:
Am 12.12.2012 23:35, schrieb Hin-Tak Leung:
--- On Wed, 12/12/12, Josh DuBois <duboisj(a)codeweavers.com> wrote:
wine-mono.
On 12/12/12 4:27 PM, Hin-Tak Leung wrote:
I am somewhat curious about the tar ball - why is the version 12 source (120MB) and so much bigger than the previous (44MB)? I can probably work it out by downloading and unpacking both, but I am feeling lazy... Hin-Tak
Thank you. That makes sense - that's the size of mono thereabouts. I guess my next question is, does it also have codeweaver-specific bits? Sorry this sounds rather lazy, but I am sure more than one person wants to know :-).
I bet it has as things without change like wine-gecko are not included. the problem is without a clean wine-mono checkout it's hard to see what changed, a folder with patches in addition would be great.
--
Best Regards, André Hentschel
Yes, I guess I'd be happier downloading a diff (against a specific "clean" upstream version), than downloading a big tar ball, then try to work out which upstream version it forked against, then do the diff myself. Even if the diff is nothing beyond a diff, with a branket description: "diff against upstream wine/mono version/tag x.y.z".
Thank you. That makes sense - that's the size of mono thereabouts. I guess my next question is, does it also have codeweaver-specific bits? Sorry this sounds rather lazy, but I am sure more than one person wants to know :-).
There are no CrossOver-specific changes to wine-mono. It's even the same build.
participants (5)
-
André Hentschel -
Hin-Tak Leung -
Josh DuBois -
Ken Thomases -
Vincent Povirk