Hi Steve, Thanks for your reply! Usually i would be tempted to get to the bottom of this and understand where/what mistakes were made (and by who;). But other than switching between Debug/Release i hadn't touched the build-settings at all, so i figured the problem couldn't be there..
But meanwhile i did managed to 'fix' the issue by clearing Xcode's caches ( XCode-app-menu > Empry Caches ). Appearanly some things got corrupted and/or confused on that level. As a nice bonus, i also got about 10Gb of diskspace back. So i have no clue what the real problem was, but it's fixed. thanks, arri On Tue, Jul 5, 2011 at 9:17 PM, Steve Christensen <puns...@mac.com> wrote: > For the nonexistent method warnings, your project- or target-level settings > likely have "Undeclared Selector" checked in the GCC warnings section of the > build settings. > > For the multiple selectors warnings, look at the Strict Selector Matching > item in the same section. It says this will pop up if you're trying to send > the message to a variable of type id, vs to an explicit class type. > > > On Jul 3, 2011, at 6:16 PM, arri wrote: > >> Hi Motti, >> >> I would be very interested to know how you resolved this issue, if at all. >> >> I'm suddenly facing the same issue, out of no-where. Instead of trying >> to find the source of the problem, I just reverted to the last known >> working version (svn), but the warnings persist. >> This surprises me a bit, because earlier today i had cleaned the >> project and made a release-build for distribution to the client, and >> this went fine. >> >> I'm sure i'm overlooking something very obvious and stupid. Does >> anyone have an idea what that could be? >> >> thanks, >> arri >> >> >> On Mon, Jan 25, 2010 at 12:04 PM, Motti Shneor <mot...@waves.com> wrote: >>> Hi everyone. >>> >>> I'm building static library, whose outward API is plain "C", and whose >>> implementation is Cocoa-based. >>> >>> It was building and working alright, until (yesterday) something changed, >>> and any attempt to clean/build/rebuild it produces huge amount of >>> compilation warnings, on EVERY Obj-C message. >>> >>> First, there's a bulk of warnings like this: >>> >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:224: warning: creating selector >>> for nonexistent method 'openPanel' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:196: warning: creating selector >>> for nonexistent method 'release' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:193: warning: creating selector >>> for nonexistent method 'code' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:190: warning: creating selector >>> for nonexistent method 'savePanel' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:190: warning: creating selector >>> for nonexistent method 'alloc' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:171: warning: creating selector >>> for nonexistent method 'stringWithFormat:' >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:160: warning: creating selector >>> for nonexistent method 'getCString:maxLength:encoding:' >>> >>> Then another bulk of warnings, complaining about DOUBLE definitions for >>> Cocoa methods!!!! >>> >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:244:0 >>> /Volumes/Data/.../FileManager_GUI_Mac.mm:244: warning: multiple selectors >>> named '+isVertical' found >>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSSplitView.h:30:0 >>> >>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSSplitView.h:30: >>> warning: found '-(BOOL)isVertical' >>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSSliderCell.h:59:0 >>> >>> /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSSliderCell.h:59: >>> warning: also found '-(NSInteger)isVertical' >>> >>> >>> >>> Notes: >>> The project is building Intel-only Universal (32/64bit, architectures i386 >>> and x86_64 >>> I only #import <Cocoa/Cocoa.h> once, in a single source file (an interface >>> header file). >>> I added (linked) the Cocoa Framework once in the project, referencing the >>> "Current SDK". >>> The project DOES compile, and even works. >>> If i turn on the "Build Active Architecture Only" build option for the >>> project (ONLY_ACTIVE_ARCH = YES) then I only get the warnings when I >>> compile 32bit. 64bit compilation is free of warnings. >>> >>> >>> These warnings worry me, as I might be using a wrong framework, and the >>> code may break on a user machine. >>> >>> Any idea will be greatly appreciated. >>> >>> >>> Motti Shneor >>> ------------------------------------------ >>> Senior Software Engineer >>> Waves Audio ltd. > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
