Mac OS X cross compiler

Erik van Pienbroek erik at vanpienbroek.nl
Tue Aug 16 18:10:46 UTC 2011


Ruben Van Boxem schreef op di 16-08-2011 om 13:43 [+0200]:
> Hi,
> 
> I have recently been put on the trail of your effort to provide a Mac
> OS X cross-compiler from Linux to Mac OS X. Although I'm running Arch,
> with the necessary symlinks(for openssl libs and /usr/darwinx) I can
> run your extracted rpms as a sysrooted toolchain.
> 
> I am wondering what the intended future of this project is. I Believe
> it is already pretty usable, and would allow cross-compiling devs to
> expand their realm to Mac OS X.
> 
> If there is still interest in further development, I would like to
> make a suggestion/feature request: the macports project seems to be
> able to supply a GCC 4.6 compiler for Mac OS X. Would it be possible
> to do the same thing here?
> 
> Thanks for the great work!
> 
> Ruben

Hi Ruben,

Thanks for your interest in the darwinx toolchain.

The toolchain as it is now works fine albeit with some small nitpicks.
The most important issues which still surround this toolchain are the
legal part and the fact that support for debug symbols in binaries is
broken due to the absence of the source code of the dsymutil tool.

I wasn't aware that the macports project is using gcc 4.6 for Mac OS X.
The main question I have with using gcc 4.6 is whether it works stable.
Apple decided to fork gcc 4.2 and heavily patch it for optimal support
for Mac OS X (this version can be found on the Apple website). Most of
those patches haven't been upstreamed AFAIK (as they're only useful for
Mac OS X) so I wonder if a clean gcc 4.6 is able to build binaries for
Mac OS X and if they're stable. Do you know anything about this subject?

Perhaps switching to gcc 4.6 will also get debugging symbols working, so
it sure is interesting to do some more research :)

Kind regards,

Erik




More information about the mingw mailing list