site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com I would recommend putting the files in your plug-in's bundle. NSBundle *bundle = [NSBundle bundleForClass:[self class]]; Dave On Aug 23, 2007, at 11:15 AM, Hugh Denman wrote: Hi everybody, Any suggestions gratefully received... Hugh -- hdenman@cantab.net +353876290136 _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... The sample FxPlug plug-ins and XCode templates show how to get to your bundle. The examples need to access their bundles in order to display localized strings. You get your bundle reference from within your plug-in like this: Then you can use NSBundle instance methods to get things from within the bundle folder. For example: NSString *path = [bundle pathForResource:@"MyLibrary" ofType:@"dylib"]; I have an FCP plugin that depends on a dynamically linked dylib, opened with dlopen / dlsym. Can anyone suggest what the best way to deploy these two files as a package is? At the moment, I'm specifying an absolute path to the .dylib in my call to dlopen, but I'd rather it was packaged in the plugin bundle somehow. This email sent to site_archiver@lists.apple.com