Thanks for the reply. However, it all seems to be in place. MyProject->'Ljnk Binary with Libraries’ = MyFramework MyFramework->'Ljnk Binary with Libraries’ = libMyLibrary.a
MyFramework contains MyLibrary.h I’ll look into the class symbol potential issue you raised... but it was a fresh project I haven’t touched anything like that Could a dodgy certificate affect this? I don’t see why so, but a few posts online have led me down that path. I feel like something is up with my copy of Xcode or it’s setup, because I have exhausted every avenue I can think of. > On 6 Feb 2017, at 22:22, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Feb 6, 2017, at 2:04 PM, Mr steve davis <southwestmons...@googlemail.com >> <mailto:southwestmons...@googlemail.com>> wrote: >> >> Undefined symbols for architecture x86_64: >> "_OBJC_CLASS_$_MyLibrary", referenced from: >> objc-class-ref in ViewController.o >> ld: symbol(s) not found for architecture x86_64 > > This is a link error, not a compile error, so it has nothing to do with > headers. Basically the linker can’t find the MYLibrary class anywhere. > Either your app target isn’t linking with your framework target (look in > Build Phases | Link Binary With Libraries), or the framework target doesn’t > contain the class MYLibrary, or the framework isn’t exporting the MYLibrary > class symbol (unlikely, since framework targets export all symbols by > default.) > > —Jens _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com