Then I have to wait to a caritative soul, because I don't have the skills yet 
to do it.

I will "play" from a virtualized windows at home until then.


----- Mensaje original -----
De: Wolfgang Lux <[email protected]>
Enviado: viernes, 23 de enero de 2009 12:55
Para: "Giuseppe Luigi Punzi Ruiz" <[email protected]>
CC: "Adam Fedor" <[email protected]>; "[email protected]" 
<[email protected]>
Asunto: Re: Building on OSX

Giuseppe Luigi Punzi wrote:

>> If you use gnustep-startup, they are compiled to be stand-alone  
>> (i.e. separate from Cocoa). FYI, GNUstep will compile on 10.5, but  
>> it won't work, AFAIK.
> DOH! If don't work, then I don't need this. Obviosly, the idea is  
> share code between
> my Windows <-> OSX machines.

It is possible to get up a working GNUstep system on OS X, but doing  
this is non-trivial. The issue on OS X is that we have two  
conflicting Objective C runtimes, the GNUstep one and the Apple one.  
Having both linked with your program almost instantly leads to a  
crash. Unfortunately, since OS X 10.4 Apple's CoreFoundation library  
uses Apple's Objective C runtime and a lot of open source projects  
nowadays make use of Apple specific features on OS X, which (directly  
or indirectly) use CoreFoundation.

Maybe somebody will have a look at making GNUstep work with Apple's  
Objective C runtime (i.e., an apple-gnu-gnu combo), but until then,  
you'll have to be brave (and a bit masochist :-) in order to find out  
all GNUstep dependencies that use CoreFoundation on OS X and either  
disable them during GNUstep's configuration or recompile them in a  
way such that they don't use Apple specific features.

Wolfgang



Enviado usando Real Mail de Vodafone.


_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Reply via email to