mattt/AnyJSON

Unsupported CPU Build Error

GQAdonis opened this issue · 9 comments

GQAdonis commented

I am trying to use AnyJSON with other CocoaPods on iOS 7 and Xcode 5, and I am getting Unsupported CPU errors when trying to build.

0xced commented

I suggest you to move away from AnyJSON and use NSJSONSerialization instead which is available since iOS 5.0. I will try to have a look at this error anyway but don’t count on it.

GQAdonis commented

It is a dependency if another library I am using (SignalR-Objc), so while I
can write around it, I become incompatible with that code base...

I will do that in the short term...

On Monday, November 11, 2013, Cédric Luthi wrote:

I suggest you to move away from AnyJSON and use NSJSONSerializationinstead which is available since iOS 5.0. I will try to have a look at this
error anyway but don’t count on it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-28229406
.

Travis James
Chief Technology Officer
CloudMetal
travis@cloudmetal.com
214.449.8711

mattt commented

@0xced What if we threw a giant #ifdef around the whole thing to only conditionally compile on targets <= iOS 5? (Maybe with another macro to #define to override, like NO_REALLY_DO_THIS_ASM_MAGIC)

0xced commented

@mattt AnyJSON was fun but hey, people really shouldn’t use it anymore in late 2013. I think the best thing to do is something like Three20 or FontReplacer, i.e. officially discontinue AnyJSON by deleting all source code and suggest to use NSJSONSerialization as a replacement.

0xced commented

Good news, as of DyKnow/SignalR-ObjC@fd41ca5, SignalR-ObjC is not using AnyJSON anymore. ;-)

GQAdonis commented

Thanks! I must have an old build and need to update...

On Monday, November 11, 2013, Cédric Luthi wrote:

Good news, as of DyKnow/SignalR-ObjC@fd41ca5DyKnow/SignalR-ObjC@fd41ca5,
SignalR-ObjC is not using AnyJSON anymore. ;-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-28252394
.

Travis James
Chief Technology Officer
CloudMetal
travis@cloudmetal.com
214.449.8711

0xced commented

By the way, you can use this specific version of SignalR-ObjC by doing this in your Podfile:

pod 'SignalR-ObjC', { :git => 'https://github.com/DyKnow/SignalR-ObjC.git', :commit => 'fd41ca5d2e5e2c79bdcb9dbcc99fe9e8f34e7564' }
mattt commented

@0xced Personally, I think we could stand to wait for another major iOS release before officially retiring this beautiful monster. Believe it or not, I still hear things about iOS 4 support for other projects.

But yeah, if things are actually broken with the latest set of tools, feel free to shut this thing down. It's your decision to make, and I'll support it 100% either way.

0xced commented

For the sake of completeness, here is how it should be done on arm64: 0xced/NSUUID@8d635dd

But it doesn’t make any sense since all arm64 devices have NSJSONSerialization anyway.