Xcode 4.5 does not support generating armv6 binaries

[Lapo]

Hello guys, make sure to update to the latest API with armv7 & armv7s support.
http://www.smartfoxserver.com/download/sfs2x#p=updates

Thanks

[Prof_PP]

Thanks Lapo, you're a Legend

[Mazyod]

Huge thanks! I love you guys

[Mazyod]

OK, I just spent 20 minutes trying to get this new API to work. I haven't posted for help, because when I made a new project and linked the library it worked perfectly.

So, it turns out Xcode retained the previous library's search path. i.e I linked the new framework, but Xcode decided to compile the old library that I have somewhere on my drive. Why is that? The search path for the old library wasn't removed when I deleted it from the project:

[Prof_PP]

Yeah I found that too. But as with many things with xCode, if you completely shut it down and restart it after making the changes (not just close the project), it appears to work fine.
I guess xCode must keep lots of stuff in cache or temporary storage because this manifests itself in other issues as well.
I think Lapo would just say it is an Objective-C thing.....which he loves so much

[A51Integrated]

Always do a Project -> Clean after you replace a lib. XCode is notorious for hanging on to objects.

[Mazyod]

I am 100% sure that what you guys have said wouldn't have worked in my case.

Since I removed the old SFS framework, I have closed Xcode many, many times, shutdown my whole Mac even. Not to mention how many times I not only clean, but clean build directory (a bit more powerful).

I think that I tampered with the search paths and manually made it point to the old API when I linked it (a month ago). So, that's why it stayed, I guess.