Re: linking problem
Re: linking problem
- Subject: Re: linking problem
- From: mark <email@hidden>
- Date: Thu, 5 Jul 2007 11:32:56 +1200
- Ironport-content-filter: send-to-smtp
On Jul 4, 2007, at 1:59 PM, mark wrote:
How do I get the plugin to link against the application's
'activeView' when it loads and not the stub's?
You need to do two things:
(1) Make sure the "activeView" global is exported from the
application, for example by means of a .exp file. This will ensure
that the global is actually available for the plug-in to import.
(2) Link your plug-in directly against the application rather than
against a stub library, by specifying the application as the Bundle
Loader in your plug-in's target build settings. (Keep in mind that
you'll need to pass the path to the actual application executable as
the Bundle Loader, not just the path to the .app wrapper.) Quick
documentation is available directly in the build settings inspector
within Xcode, in Xcode 2.1 or later; you can also check the ld(1)
man page section on its -bundle_loader flag for more details.
-- Chris
I was hoping I wouldn't have to do that.
It means I have to hard-code the application location into the plugin.
If the app moves, the plugin will break.
How does apple pull it off with it's 10.X.Y SDKs?
When an app loads, globals will link to the running system, not the SDKs.
Thanks
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden