Getting gcc4.4 to work with XCode

[Prokash Sinha]

Inline ...

On Sun, Jan 31, 2010 at 9:15 AM, Ryan Schmidt <ryandesign at macports.org>wrote:

> I'm assuming you meant to send this to the list too, so I'm Cc'ing the list
> on this reply.
>
>
> On Jan 31, 2010, at 11:06, Prokash Sinha wrote:
>
> > I don't know if you could grab gcc44 source, then build it. If that could
> be done, then you could configure the tree as follows -
> > ./configure --prefix=<Your choice for the path to install>
> > make
> > make install
> >
> > This way you can have a private installation path for example
> /Users/UserId/gcc44/
> >
> > then you can always use make to build your app.
>
> Presumably you could build gcc by hand, yes. Of course the point of using
> MacPorts is to prevent you from having to figure out how to compile things
> yourself. Just "sudo port install gcc44", wait a couple hours, and it's
> done.
>
> Agree totally.

>
> > Alternative, you give the installation path that overwrites existing
> compiler or it might even create symlinks there for different versions, and
> perhaps you could use it with Xcode framework ( including the IDE)!!
>
> I really cannot recommend overwriting any component provided by Apple. It
> may not have the same functionality as the Apple version (e.g. Apple's gcc
> can build for multiple architectures simultaneously, a feature often used to
> build universal binaries, while the FSF's plain gcc cannot do this), and a
> future Apple software update (or in this case installing a later version of
> Xcode) may overwrite your changes.
>

I had !!, so yes, I also don't like the idea. While I don't know if it is
possible to direct the paths to the new installation of app using Macports
 from Xcode configuration, if it is not there then what is the use of these
Macports? It seems like it is not well integrated with Xcode or any other
framework. The best is to point to the new installation paths. Eclipse does
that dutifully.

Also there must be a way to build the gcc for two arch (i386, and ppc) and
get an universal to field this - but yes I agree, it is a detour.

Finally, If I screwed up Xcode temporarily by overwriting the gcc binaries,
the Xcode dmg should be smart enough to fix it, when I reinstall the same
Xcode version or later version of it or for the fact, any version of
Xcode... Installation should be an independent capsule - drop it on existing
installation, and it overwrites - Otherwise it is not a true installation
package - not even a raw-medium, just raw.

-pro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20100131/3ecafe08/attachment.html>