> I’m sorry, I misunderstood your post. I thought you meant that all > autocompletion wasn’t working.
Sorry-- yeah the #import thing was my question, but when you asked about errors I thought I'd ask a side question about how to make the annoying warnings go away. > I believe that the error messages come from #warning directives inside > availability macros in the SDK, and I suspect nothing can prevent those from > appearing. What deployment target is the cocos2D build using? There should > be some conditional compilation directives testing whether the deployment > target is 5.0+, but if not I’d expect that setting the deployment target > earlier would suppress the warnings. (But again I’m not an expert in this > area.) Yeah I am wanting to support iOS 4 since I have no reason not to. Like I said, those two deprecated things aren't even things I am using... But if I have to live with those two warnings, that's fine. Patrick J. Collins http://collinatorstudios.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
