Re: +[NSBundle bundleWithIdentifier:]
Re: +[NSBundle bundleWithIdentifier:]
- Subject: Re: +[NSBundle bundleWithIdentifier:]
- From: email@hidden
- Date: Mon, 10 Oct 2005 23:39:00 -0700
Is your cocoa widget plugin being called from the same app or a
different one?
If its the same....
If you keep your libraries inside your appwrapper it wont matter
how may places you move your app, it'll always find the frameworks
dylibs etc that you would need. You can set this in your target
preferences
and a copy files phase in your app building settings.
Or.. if not, you can, when your app launches just copy the .frameworks
to the /Library/Frameworks/ folder or if you don't have permission
for that,
the ~/Library/Frameworks directory, of course checking if they exists or
not first. That way you don't need an installer you just need to run
the app
at least once.
On 17/10/10, at 22:22, Lawrence Sanbourne wrote:
Hi,
I have a Cocoa widget plugin that needs to access resources (a private
framework and a Sync Services schema) that is in the main
application's bundle. I could use +[NSBundle bundleWithIdentifier:] to
access this, but I'm worried that it will not work if the user moves
the application around frequently. Is there a way to solve this other
than putting the resources in a framework in /Library/Frameworks? I
really want to avoid having an Installer app.
Thanks,
--
Larry Sanbourne
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden