Re: [Mingw-cross-env-list] Cross compiling to MacOS X (was: Mingw-w64 thoughts)

[Ben Lau]

I've been using IMCROSS... that's how I ran across mingw-cross-env actually.

The major problem with it is getting all of the Apple proprietary
libraries to link sanely.  The way they manage their headers is very
different from Linux and I find it a pain to deal with.

My primary desktop at my job is a Mac so I use that to compile... and
Apple, in their infinite wisdom, have decided that you're only allowed
to run OS X VMs legally on Apple hardware... and then only OS X
server... I don't understand why they want to make developers lives
difficult.  So for now I compile on that...

My company is currently in the process of transitioning build queues
from CruiseControl to Hudson... so I'll probably investigate setting
up my desktop machine as a Hudson slave[1] and using that to run the
builds... but I'd prefer to have all of our "building" done on a
single machine.

I believe this is what the IMCROSS work was based on... it's also interesting:

http://devs.openttd.org/~truebrain/compile-farm/apple-darwin9.txt

Ben

[1] http://wiki.hudson-ci.org/display/HUDSON/Distributed+builds
On Wed, Dec 2, 2009 at 1:47 AM, Volker Grabsch <address@hidden> wrote:
> Ben Lau <address@hidden> schrieb:
>> My primary reason for utilizing mingw-cross-env is to reduce the
>> hassle of compiling a cross platform application on multiple platforms
>> (though I have yet to find as nice a solution for OS X).
>
> Maybe the IMCROSS project could help here. It is a bit younger
> than mingw-cross-env. It doesn't provide as many packages, but
> it provides support for Win32 as well as MacOS X.
>
>    http://www.sandroid.org/imcross/
>
> Another solution might be a MacOS X running in a virtual machine.
> Maybe there's a way to just start Darwin and the GNU tools, without
> any of Apple's proprietary GUI stuff?
>
>
> Greets,
>
>    Volker
>
> --
> Volker Grabsch
> ---<<(())>>---
> Administrator
> NotJustHosting GbR
>
>
>