Database Reference
In-Depth Information
With this file placed in the root of the CVS project (which, you may remember, has the
BuggyWhipChat and ChatAPI directories as subdirectories), we can run Ant from the
command line and see the build script work:
tom Tom:buggywhipchat$ ant
Buildfile: /Volumes/Homes/Tom/buggwhipchat/build.xml
debugbuild:
[echo] Debug Build Will Go Here
BUILD SUCCESSFUL
Total time: 0 seconds
Testing xcodebuild
I know it seems like we've spent a lot of time discussing non-Xcode stuff, but now that
we've assured ourselves that the basic Ant script is working, we can start to actually
wire up Xcode to the build. Making command-line builds work comes down to un-
derstanding a few basic commands that are included in the developer SDK. The star of
the show is
xcodebuild
, which you can find in the
/Developer/usr/bin
directory. The
basic format of the command is:
xcodebuild
[-project
projectname
] [-target
targetname
] ...
[-configuration
configurationname
] [buildaction] ...
There is an alternate format that is used if you are dealing with workspaces:
xcodebuild
[-workspace
workspacename
] [-scheme
schemename
] ...
[-configuration
configurationname
] [buildaction] ...
The major difference is that the workspace version replaces the project and target spec-
ifications with the more “modern” workspace and scheme ones.
Since we're working with a workspace-based project, we'll be using the second form
of the command. Before trying to integrate it into our build system, we should make
sure that we can run the command correctly, directly from the command line:
buggywhipchat Diane$
/Developer/usr/bin/xcodebuild -workspace \
BuggyWhipChat.xcworkspace -scheme BuggyWhipChat build
=== BUILD NATIVE TARGET ChatAPI OF PROJECT ChatAPI WITH CONFIGURATION Debug ===
Check dependencies
.
.
.
=== BUILD NATIVE TARGET BuggyWhipChat OF PROJECT BuggyWhipChat WITH CONFIGURATION
Debug ===
Check dependencies
.
.
.
/usr/bin/codesign --force --sign "iPhone Developer: Diane Coder (UU7RPZZZZZ)"
** BUILD SUCCEEDED **
