Warning in xcode5

[BryanOne]

in libffi, I get these warnings
/Users/Bryan/Documents/nevermore/Pods/libffi/ios/src/arm/ffi.c:325:21: Ambiguous expansion of macro 'alloca'

but this won't happen in xocde4

[getaaron]

Related to https://github.com/atgreen/libffi/issues/62

[liubiqu]

Pods (the project) -> Pods (the target) -> Build settings

This should be done for each target.

[laurivers]

@liubiqu It does't work

[getaaron]

This appears to be fixed in https://github.com/atgreen/libffi/pull/65 - should just be a matter of time before it's merged into BlocksKit.

[zwaldowski]

It's already merged into BlocksKit, on the next branch. You can use it today. It's more that I'm waiting on libffi.

[sberrevoets]

@zwaldowski What does the next branch mean, semantically? Is it strictly experimental, potentially buggy, or safe for production?

Also, any idea how long it will be until this fix makes it to a new version of BlocksKit (so that Cocoapods can take care of it)?

[segiddins]

I've been shipping off of next since august

[zwaldowski]

next is the next releasable version, starting as unstable and moving to stable. I consider it to be mostly stable at this point; this is why I recommend its use. I was preferring to wait to get the changes to libffi merged into upstream (primarily as a way of getting the code reviewed), but feet are being dragged on that end so next might be merged into master rather soon.

[msafder]

Excuse my ignorance but how do I get the "next" release using cocoapods?
I tried adding this line to my pod file but it didn't work:
pod 'BlocksKit', 'next'
thanks!

[zwaldowski]

pod 'BlocksKit', :git => 'https://github.com/pandamonia/BlocksKit.git', :branch => 'next'

No worries, I've fought with the pod syntax for a long time.

[msafder]

@zwaldowski whew, thanks! you saved my bacon :) 👍

[zwaldowski]

Addressed in v2.2.0.