[OGo-GNUstep-Port] Cocoa Porting, was: Re: [OGo-Developer] Roadmap and Versioning

[Helge Hess]

I took out developer@, since this is a macosx/gnustep-port issue.

Fabien VALLON wrote:
> Is there a problem using gnustep-make on OSX (Nicola ?)

I don't think that there is a general problem. I invited Nicola to join 
the list, we'll see whether he finds time ;-)

> I think MOSX could use it :) 

Yes, but it might be complicate to setup since the developer needs to 
fiddle around with all those environment sourcing which is a bit 
difficult in Finder.
And the build-results should definitely be independend from GNUstep, 
that is, the build process should create frameworks and bundles usable 
without the GNUstep environment.

Nicola has shown that this can work with Renaissance.

> I'm talking about code.
> Do you plan separate cvs tree ?

Definitely not. A single codebase should work everywhere.

>>And the target audience usually is also quite different, little OSX 
>>people knowing GNUstep very well and the reverse as well.
> 
> Well GNUstep/Foundation & Cocoa/Foundation are quite the same ...

Like libFoundation. GNUstep-base differs as much from libFoundation as 
Cocoa Foundation does.

One concrete example is porting the file-descriptor handling in 
NSRunLoop, which isn't part of ObjC Cocoa, but both, libFoundation and 
gstep-base provide that. So we should use exactly that on gstep-base and 
find a good workaround for Cocoa (we currently use a hack there which 
uses NSFileHandle but seems to work fine). I think on Cocoa we might fix 
that by using CFRunLoop instead of NSRunLoop.

Anyway, people should just get started ;-)

regards,
   Helge
-- 
http://www.opengroupware.org/