David Chisnall wrote:
On 20 Jan 2011, at 15:52, Ivan Vučica wrote:
By the way, in case someone is interested in fixing MacPorts rather
than publishing an alternative and updated way to compile on OS X,
the link to MacPorts bugtracker ticket is here:
http://trac.macports.org/ticket/28063
That bug report is about not being able to compile GNUstep with
Apple GCC. This won't work, because Apple GCC can't target the GNU
runtime (clang can on OS X, so that might work, but it's untested).
GNUstep does not work with Apple's Objective-C runtime, which is
designed to work closely with Apple's Foundation.
Apple's gcc can target the GNU runtime (-fgnu-runtime), it simply
doesn't do that by default and the GNU Objective runtime system isn't
installed along with the developer tools (for obvious reasons).
I'm not really sure what the objective is in using GNUstep on OS X.
You can use GNUstep Additions to get most of the GNUstep extensions
on top of Cocoa, and you can just use Cocoa if you want the core
APIs...
You can easily test that you applications work with GNUstep and you
don't have to set up a virtual machine for that.
Wolfgang
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
