Re: implementing plugins
Re: implementing plugins
- Subject: Re: implementing plugins
- From: Greg Parker <email@hidden>
- Date: Wed, 2 Dec 2009 15:16:59 -0800
On Dec 2, 2009, at 3:04 PM, Joel Reymont wrote:
> Firefox loadable binary components ("plugins") link against dynamic libraries at the moment. Firefox links against too many dynamic libraries, though, and I have noticed a nice performance increase from a mostly static build compiled with -mdynamic-no-pic.
>
> Unfortunately, the static build breaks binary components since they no longer have dylibs to link against. Components still need string and other facilities now housed inside the static body of Firefox. Components also need to be compiled despite using undefined functions.
>
> This seems like a regular "plugin" issue, solved many times by now. I can't figure out how to solve this, though. Any suggestions?
Try the -bundle_loader flag. When building a plugin, -bundle_loader tells the linker what executable will load the plugin, so the plugin's dependencies may link to the main executable itself. Then make sure the symbol visibility options for the main executable publish any symbols that the plugins might use.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden