This change is great for shutting up Xcode 7, but 6.4 errors out on _Null_unspecified. It looks like __null_unspecified works for both. Would you mind changing these to the more compatible version?

Ok, done! Hopefully they don't deprecate "__null_unspecified" any time soon. (I don't think they're eager to.)

Fantastic! Thanks for the contribution.

If they end up dropping the nullability attributes introduced in Xcode 6.3 we will probably need our own compatibility macro. But I'd prefer not to get into that unless it ends up being recessary.

Yah, no need to go looking for trouble.

I have another thing I did where I made an Xcode project for this and for libgit2 that you can include as a subproject in another Xcode project, and it'll build on iOS or OS X automatically all inside Xcode with no external tools (e.g. no cmake, no scripts). Not sure if you guys want that, though, because the libgit2 one DOES require maintaining by the Xcode project by hand if you add / remove files.

I'm very interested in seeing this libgit2 Xcode project. Do you have it in a branch on your fork of ObjectiveGit?

I understand at least some of the issues with having a build system separate from the libgit2 cmake build, but there are a couple issues I've been looking into that I can't seem to resolve:

• git2 is not a real module, it's a submodule under ObjectiveGit (causing errors when importing ObjectiveGit as a module Including library in Swift only project is failing #436)
• bitcode support - this is pretty easy to add for one architecture, but gets dropped when we lipo the slices together

Both of these seem easy to solve with a real Xcode build.

🤘 Those warnings had been bugging me.