discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Portability/Compatability between GNUstep <---> Cocoa...


From: Lars Sonchocky-Helldorf
Subject: Re: Portability/Compatability between GNUstep <---> Cocoa...
Date: Tue, 13 Jan 2004 15:23:41 +0100

Nicola Pero <address@hidden> wrote on 13.01.2004 13:04:37:

> > That's no good. Apple's GCC always defines __APPLE__
> 
> If Apple's GCC always defines __APPLE__, that is not good, because if 
you
> are trying to use gnustep-base on Apple instead of Apple's FoundationKit
> (a task which does present difficulties, but which has been attempted 
many
> times), then Apple's GCC would still define __APPLE__ even if you are
> actually using gnustep-base.

That currently purely theoretical since you currently can't use 
gnustep-base together with the NeXT-objc-runtime. And Apples GCC is 
currently installed _without_ the GNU-objc-runtime (and i don't think this 
will change unless both runtimes are unified, see recent discussions on 
address@hidden). Therefore you'll need to build a patched* 
GCC by yourself and most people will use the FSF-GCC since the patched are 
made for this one

)* Geoff Keating of Apple managed it to hose the building of libobjc on 
Darwin:

http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01296.html

since then rants came up:

http://gcc.gnu.org/ml/gcc-patches/2003-07/msg01800.html

but afaik there is still no final solution for this. :-(


greetings Lars





reply via email to

[Prev in Thread] Current Thread [Next in Thread]