• 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: plug-in problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: plug-in problem


  • Subject: Re: plug-in problem
  • From: Shaun Wexler <email@hidden>
  • Date: Tue, 2 Sep 2003 12:12:45 -0700

On Sep 2, 2003, at 3:42 AM, Jon Hull wrote:

I am getting the following errors in the console:
1)Both XXX and YYY have implementations of class CurrentAssignment
2)objc: thread is already initializing this class!

my app then just exits with status 1. My plug is dependent on the
class CurrentAssignment, so if I only include the .h file it wont
compile. Both the plug and app need the class.

You need to place all shared classes into a framework target, and optionally embed it into your app. When the app first launches, it will utilize the framework from within its own bundle. If you need to have it available to other processes (ie tasks not plugged-in to your app), you can copy it into ~/Library/Frameworks when the app is launched, but plug-ins packaged in your app contents, or loaded as bundles by your app won't require the 2nd copy.
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
References: 
 >plug-in problem (From: Jon Hull <email@hidden>)

  • Prev by Date: Re: question
  • Next by Date: Re: Cocoa/run sudo
  • Previous by thread: Re: plug-in problem
  • Next by thread: Re: plug-in problem
  • Index(es):
    • Date
    • Thread