Hi Patrik,
Thanks for the response.
> > -> According to the "MacOS X Kernel Environment" book, pg. 37,
> > Mac OSX does not support memory mapped devices through the mmap
> > API. This would affects at least streaming sound playback.
>
> But it supports mmap for files? Especially MAP_SHARED?
I would assume that it supports mmap for files, however
I can't back that up with facts. ^_^ I say that it
probably is supported, otherwise Apple probably would list
it as a difference between it and BSD in the Mac OS X
Kernel Environment book I referred to earlier. I couldn't find info
on that in my usual places (google, deja), but someone here at
the office has a copy of MacOS X so I'll see if I can see for
myself what mmap on that platform supports.
> Speaking of mmap. Does MacOS X support sendmsg/recvmsg?
> If not you can forget about porting Wine unless you can
> convince Alexandre that the Wineserver should be redesigned.
I would assume so, but I will look for myself....
> > -> Sound Support. Currently done with WineOSS (ties into
> > Linux OSS drivers) Doesn't seem to be a port of OSS
> > to MacOSX. Maybe need to do another layer specific to the
> > Mac(?)
>
> Well. The Solaris port doesn't support sound yet so that
> is not really nessary.
It's necessary for me, because sound is an important
feature of the app I might be porting. ^_^
> That said I don't imagine support MacOS X through a special
> driver will pose any problems.
Yah, probably not, but still it is another task that will
take time.
> > -> Must ensure that behaviour of lower level UNIX resources
> > like sockets, threads, files are the way WINE expects it.
>
> Wine currently expects that the file API works on socket descriptors.
> This is not the case on BeOS but I determined that this was a
> fixable issue. I just never did it.
I would be surprised if file API didn't work on socket, since
MacOS X is built on BSD core and they ported emacs, apache, etc.
succesfully to MacOS X. But again, I should verify that.
> > -> Need to be able to build Windows app using gcc (might be issues
> > such as using MS specific keywords/language constructs, etc.)
>
> That isn't really a MacOS X specific problem is it?
No, you're right. I'm just making a list of all the things
that would have to be done to port our app, using WineLib, to Mac OSX,
and that is one of the tasks for ME.
-James
--
James Hatheway
Software Designer - Macadamian Technologies, Inc.
[EMAIL PROTECTED] ~ http://www.macadamian.com
"Nothing is a problem once you debug the code."
