changed default SDK to the current one
fixed non-literal format string warning
project update caused by opening in XC4 I think
added xc4 workspace
added xc4 workspace
Changes for Hype
Added an XPC service to deal with sandboxing.

This fixes #163. It requires that you copy the XPC service into your main application bundle in
Contents/XPCServices and runs the remove from quarantine step of copying the finish_installation
app as well as launching finish_installation app outside of the sandbox. Sparkle will function
exactly as it does now for applications that do not copy the XPC service into their application
bundle.
Merged latest from Andy's branch
Updated project settings.
Removed -fsingle-precision-constant flag which LLVM doesn't recognise
fixes for warnings thrown up by xcode 4.4 / llvm
xcode 4.4 project settings update
Merge branch 'master' of https://github.com/andymatuschak/Sparkle into integration
Merge remote-tracking branch 'wbyoung/master' into sandboxing
Merge in changes for sandboxing and XPC

Pull request here: https://github.com/andymatuschak/Sparkle/pull/165
Changes here: https://github.com/wbyoung/Sparkle/commit/dbd2b9b30aad66296fab5cf9b980bf02020fa71a
Merge current TOT from upstream
Build dSYM for XPC service
XPC service only needs to build x86_64
Remove useless build flag that's not understood by modern clang
Removed and re-added strings files

I continually get errors along the lines of "failed to remove
<string file path>: “Sparkle.strings” couldn’t be removed." The
internets suggest removing and re-adding the files "fixes" this
issue, so I did… and, yes, things seem to always build, now. Have
no clue what this really tweaked, but I'm just happy the errors
seem to have disappeared.
Set the blessed key that keeps pboxd from appearing in the Dock along side our app

If SandboxService.plist doesn't have JoinExistingSession as YES
in the XPCService dictionary, the XPC service will instantiate
its own security session, separate from the app. While this seems
inoccous, it may lead to subtle (or, in our case, not so subtle)
problems. In our case, as a sandboxed NSDocument based app, pboxd
is instantiated on launch. When our app is in a different
security session – as it would be without this key – the Dock
actually shows pboxd running alongside our app, looking like our
app. Effectively, the user sees two copies of our app but one
seems totally broken. Setting JoinExistingSession to YES makes
everyone happy.