Re: Commandline Tool Chain?
Re: Commandline Tool Chain?
- Subject: Re: Commandline Tool Chain?
- From: Kyle Sluder <email@hidden>
- Date: Sat, 17 Sep 2011 20:58:27 -0700
On Sep 17, 2011, at 12:42 PM, Paul Davis <email@hidden> wrote:
> On Sat, Sep 17, 2011 at 3:39 PM, Michael B Allen <email@hidden> wrote:
>> Does anyone at least know if Xcode just calls the GNU tool chain?
>
> fundamentally, yes.
The big thing Xcode does differently is it has its own build dependency engine (analogous to Make or Jam, which it used to use).
xcodebuild reads the project file to drive the compiler. It sets up all the requisite environment variables and flags based on the build settings and target definitions. There are a staggering number of options that can be passed to the compiler, linker, and post processing tools like codesign. And even more steps are involved if you want to build for iOS devices, in which case you cannot avoid Xcode.
So while you can invoke clang directly (don't use GCC anymore; it's unsupported) to produce fully functional Mac OS X binaries, if your main concern is being able to use vi to edit your code you are better off configuring your workspace in Xcode 4 and using xcodebuild to build your product.
Further questions of this nature might be better-suited to the Xcode-users mailing list.
--Kyle Sluder _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden