Release 0.9.0

[pietbrauer]

Release a new version: 0.9.0

Changeling (Comparison)

• Added support for typed collections ([Xcode 7] Add types to collections in GT headers #516). Thanks @JrGoodle!
• Adjusted GTMergeAnalysis type to use NS_OPTIONS (Adjusted GTMergeAnalysis type #522). Thanks @slavikus!
• Silence umbrella header warnings (Xcode 7 + silence stupid warning #523). Thanks @joshaber!
• Remove isGitDirectory: (Remove isAGitDirectory: #527). Thanks @pietbrauer!
• Expose moveHEAD (Fix libssh2 inclusion in libgit2 iOS build script #533). Thanks @phatblat!

[phatblat]

Wow, some of those changes have been sitting around for a while. Thanks for bringing this up, @pietbrauer!

[joshaber]

I created a 0.8.9 release (https://github.com/libgit2/objective-git/releases/tag/0.8.9) but I haven't been able to create a binary for it. When I try, I get:

target 'Nimble-iOS' has bitcode disabled (ENABLE_BITCODE = NO), but it is required for the 'appletvos' platform

Possibly the same as SwiftJSON is seeing: SwiftyJSON/SwiftyJSON#327 (comment)?

Any ideas? Anyone else able to create a binary? (carthage build --no-skip-current)

[pietbrauer]

Sweet, can try tomorrow. Why 0.8.9 though? Isn't the NS_OPTIONS change is a breaking change?

[joshaber]

Why 0.8.9 though? Isn't the NS_OPTIONS change is a breaking change?

Good point. I was thinking it was just fixing a bug, but I guess it does break anyone who was using it. 👍

Updated to be 0.9.

[phatblat]

With watchOS and tvOS being part of "all" platforms now in carthage, we should probably use the following when building dependencies:

carthage build --platform Mac,iOS

[joshaber]

Ah interesting. So that gets me a bit further, and then a lot of errors like:

/Users/joshaber/Documents/Development/GitHub/objective-git/Carthage/Checkouts/Nimble/Nimble/Nimble.h:1:9: note: while building module 'Foundation' imported from /Users/joshaber/Documents/Development/GitHub/objective-git/Carthage/Checkouts/Nimble/Nimble/Nimble.h:1:
#import <Foundation/Foundation.h>
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:10: note: while building module 'CoreFoundation' imported from /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:
#include <CoreFoundation/CoreFoundation.h>
         ^
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:11:10: note: while building module 'Darwin' imported from /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:11:
#include <sys/types.h>
         ^
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "sys/cdefs.h"
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/usr/include/sys/cdefs.h:707:2: error: Unsupported architecture
#error Unsupported architecture

[phatblat]

I don't get these errors building with Xcode 7.2 and carthage 0.11.0 (on OS X 10.11.2) using the following command:

carthage build --no-skip-current --platform Mac,iOS --verbose

Build log: https://gist.github.com/phatblat/e6525b198bff64dfa738
Build: http://b.log-g.co/eCNa

[joshaber]

¯_(ツ)_/¯

I uploaded that build. Thanks to you both!

[phatblat]

A couple differences between that .zip file and the 0.8.8 release:

• not codesigned
• .dSYMs not included (I removed these to make the file smaller)

[joshaber]

[joshaber]

So should I remove the binary?

[phatblat]

I don't think either of these are problems. The README states:

dSYM files are not currently included in the GitHub release zip files

As for codesign, iOS apps need to sign embedded frameworks anyway before deployment. I'm not sure about Mac apps. So, I think the file I provided is fine, just not 100% sure since I typically build ObjectiveGit from source.

@pietbrauer lmk if you have any problems with the new build.

[pietbrauer]

Works, thanks guys! Such a bliss to work with it in Swift now.