[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] Separate build rules (was Re: Mingw64)
From: |
Volker Grabsch |
Subject: |
Re: [Mingw-cross-env-list] Separate build rules (was Re: Mingw64) |
Date: |
Mon, 12 Dec 2011 11:29:34 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Volker Grabsch schrieb:
> Tony Theodore schrieb:
> >
> > GNUstep is still alive and well:
> >
> > http://lists.gnu.org/archive/html/discuss-gnustep/2011-11/msg00113.html
> [...]
> Has anyone here use it in combination with Qt?
> Is it possible to cross compile a Qt application for MacOS X without
> the proprietary SDK from Apple?
I had a look at GNUstep, and I think I can answer
my question: No, it doesn't help. :-(
GNUstep is great if you have an application that uses
the native OS X API (Cocoa etc.) - it helps you to compile
the very same source code natively on the Mac as well as
for Linux/*BSD.
However, it doesn't seem to be of any help if you want
to compile for the OS X target. You still need Apple's
proprietary SDK for headers, etc.
On the other hand, it *might* be possible to derive some
kind of "simpler, but free" drop-in replacement for the
Mac SDK. But that's a question for a GNUstep mailing list,
I guess. Any voluteers are welcome. ;-)
Anyway, I would I'll be able to setup some OS X cross
compiling environment in the near future. But there
currently more urgent issues in the mingw-cross-env
project.
BTW, what about renaming mingw-cross-env to something
like "MCE" or "m-cross-env"? The "M" could then stand
for "MinGW" als well as "Mac OS X". ;-)
Greets,
Volker
--
Volker Grabsch
---<<(())>>---