Re: Cannot produce executable target for command line tool in xcode 4.3
Re: Cannot produce executable target for command line tool in xcode 4.3
- Subject: Re: Cannot produce executable target for command line tool in xcode 4.3
- From: Jens Alfke <email@hidden>
- Date: Thu, 19 Jul 2012 09:54:29 -0700
On Jul 19, 2012, at 7:28 AM, Joe Armstrong <email@hidden> wrote:
> I assume you mean the thing that when I hover over it says in yellow "show the log navigator"?
> but I can find no "build log" (in an earlier mail you said it was "one of the tabs on the organizer"
> but the organizer is on the far right button) ...
The person who replied to you got the terminology a bit mixed up; once you use this stuff a lot you stop thinking of what they named the different pieces and just use them.
> Actually I do think this is hard since it involves several non-obvious steps. I did "click around a bit" last night (about two hours) and couldn't find what I wanted - that's why I joined this group - and thankfully got a quick reply to my question.
I hate to sound like one of those snooty guys who grunts "RTFM", but have you read the Xcode User Guide, or are you just diving in trying to figure stuff out? The user guide doesn't go too deep, but it seems pretty broad, covering pretty much every aspect of the UI. There are also quite a lot of books nowadays that cover using Xcode for Mac or iOS development.
> I'm old school - I expected the default directory for executables is the directory where I the code was.
IMHO it's a real mess for the compiler to just poop out its output all over my source directories (especially intermediate stuff like .o files.) I appreciate that Xcode tries to keep stuff organized, although I disagree about the details (I hate that the build output is now about six layers deep inside the build folder when it used to just be two.)
Also keep in mind that Xcode is optimized for building applications, not command-line tools. (Well, it does get used a lot at Apple for building the OS itself, but every component builds into its own output directory tree and then those are assembled together into an OS image.)
> Now this should be easy in objective C and X code - but all this stupid callback nonsense makes it
> horrendously complex - this grand central dispatch nonsense is a mess to make callback programming
> a tad less objectionable.
It's a matter of taste, I think. I've tried to use Erlang (for work; I'm at Couchbase) and found the basic language straightforward but the system as a whole utterly impenetrable, a twisty maze of little processes all alike. I find blocks much easier to follow. Some of this may be my history (I cut my teeth on Smalltalk back in the early '80s), but the popularity of Node.js implies others feel similarly. Anyway, that's off topic...
> Actually all I want to do is use the audio units on the mac which are awesome.
> All I want to say is " Instrument ! {playNote, ....}" and for a sound to be played - …
Oh boy. The Core Audio APIs are hideously complex and difficult to use, and all based on super-low-level C constructs. Definitely one of the two most frustrating APIs I've ever used (the other is the Security framework / CDSA.) Now, the newer AVFoundation framework looks a lot higher-level and cleaner, so hopefully it's easier to use. I'd recommend starting there.
—Jens
_______________________________________________
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