On Jun 12, 2015, at 14:17 , Patrick J. Collins <[email protected]> wrote: > > I have no errors.. only 3 warnings, and they are coming from my 3rd > party library Cocos2D:
I’m sorry, I misunderstood your post. I thought you meant that all autocompletion wasn’t working. I’d have to assume it’s something to do with the way Xcode deals with header paths, but I don’t have any knowledge of this area. > Apple Mach-O Librarian Warning: > > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: > file: > > /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/lib/libz.dylib > is a dynamic library, not added to the static library I dunno, it sounds like something is explicitly trying to link zlib into cocos2D. You can try looking at the full build transcript to see if it offers any clues as to why it’s doing that. Note however that (AFAIK) you have a genuine problem here. Many open-source libraries don’t preserve API compatibility across versions, which means your cocos2D static library build really ought to link in a static library build of the zlib version it requires, and not rely on the version that gets linked automatically by Xcode. > Deprecations: > > > /Users/patrick/MyProject/Externals/cocos2d-iphone/cocos2d/CCProtocols.h:158:24: > 'UIAccelerometer' is deprecated: first deprecated in iOS 5.0 - > UIAccelerometer has been replaced by the CoreMotion framework > > > /Users/patrick/MyProject/Externals/cocos2d-iphone/cocos2d/CCProtocols.h:158:71: > 'UIAcceleration' is deprecated: first deprecated in iOS 5.0 - > UIAcceleration has been replaced by the CoreMotion framework > > These warnings came up after switching to XCode 6, which I am a little > confused by because I have XCode's project settings for Cocos2D "Inhibit > all warnings" - YES, as I am not using UIAcceleromter or UIAcceleration > in my project. > > As a side question, any idea how I can make these 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.)
_______________________________________________ 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]
