Re: Is xcodebuild install output complete?
Re: Is xcodebuild install output complete?
- Subject: Re: Is xcodebuild install output complete?
- From: Scott Tooker <email@hidden>
- Date: Wed, 5 Jan 2005 15:43:10 -0800
Currently, no. The detailed build ouput is not a complete transcipt of
what goes on during a build.
In the future we want to get the build log transcript to the point that
you could take the output and run it in the terminal, but we are not
there now.
It's unfortunate that you don't have the time to provide bug reports on
the issues that make using Xcode difficult for you. Even if you can't
justify the bug reports, constructive e-mail to
email@hidden about the issues that keep you from
using Xcode would be greatly appreciated.
Scott
On Dec 1, 2004, at 1:08 PM, Eric Ocean wrote:
I've read the man page, Apple's developer pages, etc. Is the output
I'm seeing in my terminal everything I need to duplicate what
xcodebuild install is doing in another build tool? Or are there hidden
environment variables and who-knows-what-else that I'm not seeing? Any
magic going on?
Best, Eric
P.s. If you're tempted to suggest that I continue to use Xcode and
xcodebuild, please read on before replying:
- I don't want to use xcodebuild install. I've _been_ using it, and
I've made a rational decision to cease using it and Xcode for Cocoa
development. After releasing two applications, I can't waste any more
time on those tools. If you're qualified to write code, you're
qualified to manage a build down to the smallest detail. I know what
result I want and communicating that to Xcode and xcodebuild in a
reliable way has proven not to be possible for me. They've moved from
help to hinderance.
- Since switching to TextMate (from BBEdit and Xcode), my coding speed
has doubled (literally). It's a pain to manage Xcode and TextMate at
the same time. I took up Ruby a few months ago and now I'm a
script-writing maniac. I use it for everything. I've started embedding
Ruby code (via ERb) in my C source and evaluating it before sending it
to the compiler. It works great: no more preprocessor suffering. Xcode
and xcodebuild are just the last to go. (I'll still use IB though :-).
I'm moving my Cocoa builds to use Rake, a make replacement written in
Ruby. Very cool.
- I don't want to file more bug reports, feature requests, or
usability enhancements. It takes 15+ minutes to file a useful one, and
I just don't have that much time. The hours I work need to actually
_produce_ something, not be spent on charity (as much as I'd like to
see Apple succeed).
- I think Xcode has potential and I encourage Apple to continue
working on it. Fix-and-Continue and ZeroLink are cool. I'd probably
like distributed builds, too.
- At the end of the day, I just have to earn a living. Given the
amount of time I've expended working around problems with the tools,
*I* can't continue to justify the expense. Your milage may differ :-).
_______________________________________________
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
_______________________________________________
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