Fwd: Linking to a Mac OS X build of Wine from winehq.org/download ?

Zach Drayer zach at drayer.name
Mon Dec 22 17:14:17 CST 2008

Begin forwarded message:

> From: "Austin English" <austinenglish at gmail.com>
> Date: December 22, 2008 6:12:13 PM EST
> To: "Zach Drayer" <zach at 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 at 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.

More information about the wine-devel mailing list