Re: Missing GNU tools -- who needs em'?

Interesting. I didn't realize those were shipping non-autoconfiscated
tarballs. I've certainly needed autotools myself in the past, for
projects where I was doing development work, as opposed to relying on
their distribution tarballs, but I've always needed newer ones than
Apple shipped, so I've never relied on the ones that came with Xcode.
Autoconf, in particular, seems to have this problem frequently.

I've never had a hard time installing autotools from source.

As to your other point, to me it feels like non-C languages are more
"first class" than ever with the emergence of scripting bridge.
Packaging projects that rely on interpreted languages for distribution
to end users is as much of a challenge as ever, but using those
languages for serious development feels better now than it has for a
long time, IMO.

Geoff

On Sun, Apr 1, 2012 at 21:34, Joe Hodge <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I ran into the problem of missing "autoconf" while trying to install the
> latest Ruby and Python as I wanted to see if they where appropriate for a
> translation program I wanted to do. And yes, I feel constrained when given
> no other up-to-date programming languages other than the "C family". I
> started my first major app on a Lisa booting the Mac OS from disk back in
> the '80s writing in modula-2. I would like to try Eiffel since reading
> what's-his-name's book on it years ago when C was the "only language
> acceptable" for large projects. lol! I don't like to see innovation stifled
> on the Mac.
>
>
> On Tue, Mar 27, 2012 at 16:53, Rick Mann <[EMAIL PROTECTED]> wrote:
> On Mar 27, 2012, at 13:48 , Joar Wingfors wrote:
>
> It depends on what you mean with the "GNU tool chain". That said, it's
> correct that autoconf/automake was dropped from the Xcode distribution
> starting with Xcode 4.3.
>
>
> I'd argue that this is a bad move. Why did Apple do this? It's a real PITA
> to have to install a bunch of GNU tools to let open source projects build.
>
> Out of curiosity, what projects require you to install
> autoconf/automake just to build? Most ship autoconfiscated tarballs
> that don't require the tools to be installed just for building. Many
> require the tools available to hack on the projects, but they often
> require specific versions of the tools that are generally newer than
> what Apple was shipping anyway, so the apple-shipped versions didn't
> relieve the need to install them and actually made things more
> challenging in some cases.
> I deal with a fair few autotools-driven projects, and I can't say I'm
> even a little sorry to see them go from Xcode installations. Can you
> link to a problem project?
> Geoff

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/alexiscircle%40gmail.com

This email sent to [EMAIL PROTECTED]