Re: Experiences with MacPorts of GNUstep

[address@hidden]

On 11 Mrz., 04:14, Adam Fedor <fe...@qwestoffice.net> wrote:
> On Mar 10, 2008, at 2:04 PM, Adam Fedor wrote:
>
> > I'm hoping to update the port files sometime (perhaps after I make  
> > all the new releases).  For one thing, you don't need FSF gcc  

Ah, that is good to hear! Do you think you can take over the role of
the official maintainer of the MacPorts portfiles? If you need help, I
will do as much as I can.

> > anymore.  That should save a lot of time, at least.
>
> Actually, it appears you do need FSF gcc on 10.5, unless I can figure  
> out how to revert the compiler back to Objective-C 1.0

On the Mac, the installed compiler depends on the Xcode version and
the system version. But it is quite safe to assume 10.4.x with Xcode
2.4 or 2.5 and 10.5 with Xcode 3.x. The different gcc versions are
installed through Xcode and there are compatibility SDKs. I think
there is still 10.3.9 in Xcode 3.0 which uses a gcc-3.x.

But the issue is that all this depends on the Xcode installation and
MacPorts can't change that. I think we can only add rules that check
the correct compiler and install the FSF compiler if it does not fit.

Another point might be which Obj-C runtime will be used for GNUstep on
MacPorts. Apple's gcc always assumes the Mac runtime. And, to be
independent from that, we still have to install FSF gcc.

Although the installation time was high (2 hours on a DualCore MacBook
Pro), this is IMHO not a critical barrier. If installation works.

What I have also read is that MacPorts can somehow create binary
installers for packages. Maybe, we should not only maintain the
portfiles but always publish new binary packages. If they need to
include FSF gcc or not doesn't really care.

What we also need to add (but one after the other) is GSCoreData and
SWK plus Vespucci.

-- hns