Re: SOT: g++ (command line) problem
Re: SOT: g++ (command line) problem
- Subject: Re: SOT: g++ (command line) problem
- From: Greg Guerin <email@hidden>
- Date: Tue, 19 Jun 2007 16:09:36 -0700
David Goldsmith wrote:
>Actually, I'm using the command line because I was having zero luck using
>Xcode, and that was way, way too big a behemoth to figure out; from where I
>stand, it seemed (still does) to make more sense to learn how to start the
>engine, then learn how to drive the car.
Either way, you have to ask the right questions.
Your initial post came across as being from someone with a decent amount of
command-line experience, and thus probably having a reason for using the
command-line instead of Xcode. Since this is a list about Xcode, not
command-lines, I even thought the question was a minor detail in some
larger Xcode-oriented context, such as how to use g++ in a shell-script
build phase.
You may find this article generally useful in phrasing questions:
<http://www.mikeash.com/getting_answers.html>
I also recommend clarifying what experience you have with Unix command-lines.
Neither bash nor *csh are simple command-line interpreters. In fact, each
one is a complete programming language, and a "command-line" is really a
statement in the shell programming language. If you don't have any
experience with them, they are tough nuts to crack, not least because so
much is hidden or obscure.
The shell looks simple ("Hey, it's just a command-line"), but it's
deceptively deep and complex, and there are many dark corners that still
puzzle and surprise me, even after 20+ years using Unix shells. Xcode
looks like more of a behemoth, but that's at least partly because more of
it is graphically visible. Starting with the shell can be like having to
build an engine from random parts, including machining your own camshaft
from a solid chunk of steel, then installing it in a car chassis you built
in your spare time, before you can begin to learn how to drive.
If you had zero luck with Xcode, you'll have to be specific about exactly
what you tried, and exactly what the error was when it didn't work.
Statements like "zero luck using Xcode" are too vague to reply to, except
with generalized responses like "Try a tutorial".
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden