• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Carbon-Cocoa Integration: Linking issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Carbon-Cocoa Integration: Linking issue


  • Subject: Re: Carbon-Cocoa Integration: Linking issue
  • From: Shripada Hebbar <email@hidden>
  • Date: Tue, 22 Jan 2008 10:10:34 +0530


My first instinct was to #import the header file, but that had resulted in much more inscrutable errors -- and moreover, I saw elsewhere on this list that you were supposed to import implementation files in these cases. Okay, fair enough...
Hmm...Thats indicative of a bad practice and can always be resolved and avoided by
properly importing headers and adding appropriate source files to the target.




So here are the "inscrutable" errors, once I import the header file
for MyController:

Undefined symbols:
 "_InnoveghtiveFileDestroyer", referenced from:
     _InnoveghtiveFileDestroyer$non_lazy_ptr in MyController.o
 "_ProcessFile", referenced from:
     -[MyController processUserFile:] in MyController.o
ld: symbol(s) not found

The first is referring to an extern NSString that I declare in
MyController.h. It causes no issues when this file is compiled as part
of my regular app build.
Can you be more descriptive on the builds/targets you are mentioning? Its not clear
as how many targets you have and the purpose of them. It seems like you have one
target which is a simple cocoa application in which you have the MyController. And you have
another target which is the plugin. And you are trying to use some functionality of your cocoa app
to test the plugin out. Is that what you are trying to do?


Interestingly, the second error is talking about a method call that I
don't even use in the Carbon code. But again, it's properly declared
in the header file, and causes no issues in the main build.
Did you try including the implementation file containing the method code as well into the target?

Regards
Shripada

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Carbon-Cocoa Integration: Linking issue
      • From: "Aaron Vegh" <email@hidden>
References: 
 >Re: Carbon-Cocoa Integration: Linking issue (From: Shripada Hebbar <email@hidden>)
 >Re: Carbon-Cocoa Integration: Linking issue (From: "Aaron Vegh" <email@hidden>)

  • Prev by Date: Re: AW: leopard: No universal libjpeg.dylib in 10.4SDK?
  • Next by Date: NSAppleEventDescriptor - getting a double (and other animals)
  • Previous by thread: Re: Carbon-Cocoa Integration: Linking issue
  • Next by thread: Re: Carbon-Cocoa Integration: Linking issue
  • Index(es):
    • Date
    • Thread