As of Firefox 6.0, Mozilla no longer supports building it against shared xulrunner. You may or may not already noticed that. For some users, this simply means that your next
--depclean will unmerge last install of xulrunner. For some others, this means you will be building two copies of the same thing — one for Firefox, and the other for a few packages depending on xulrunner.
One especially painful case here are browser plugins. Right now, their ebuilds mostly depend on the whole xulrunner being built while that’s not exactly true for the packages itself. In fact, building Netscape plugins requires only headers to exist — no linkage is necessary, all necessary symbols are provided by the browser itself (and if they aren’t, the plugin probably won’t work anyway).
For all that, I really don’t see a reason to waste like 1 hour compiling an awfully large package just to use its headers for a few minutes and then have no real use for it. That’s why I decided to try establishing a tiny package containing headers and pkg-config files necessary to build plugins.
How packages build Mozilla plugins?
Most of browser plugins are actually clear NPAPI plugins. In simplest words that means that they need four standard, well-established
np* headers to be built. These could be found, for example, in the npapi-sdk package.
And in fact, some projects actually bundle that four headers. That’s the best case because it means that a particular plugin has no xulrunner/mozilla dependency. It just builds the plugin against bundled headers and we don’t have to worry about supplying them to it.
When packages rely on external NPAPI headers, the pain begins. All these years, Mozilla upstream didn’t really establish a clear way of finding them. Each package has its own autoconf for it, less or more complex, and less or more wrong.
A good example here is VLC. It provides a quite painless method looking either for
libxul or one of
*-plugin pkg-config packages. Not sure, however, if most of names used there really existed but
mozilla-plugin is the one most commonly used.
Either way, that test always nicely succeeds with xulrunner and lets VLC find its headers. If we establishing a tiny NPAPI header package, and just use
mozilla-plugin pkg-config file in it, VLC will build fine against it. Sadly, if
libxul is in the system, VLC will use it and link the plugin with it — for no reason.
gnash is another good example here. Although the code may look a little scary, it uses
mozilla-plugin pkg-config and doesn’t link against anything.
On the other hand, gecko-mediaplayer is an awful example here. It’s using a lot of random pkg-config checks, and relies on features based on xulrunner pkg-config version. Mostly impossible to handle clearly; we need to inject additional, hacky pkg-config file to satisfy their checks — probably for no good reason.
IcedTea-web is a totally different case here. Unlike packages mentioned before, this one uses a larger set of xulrunner headers; though still requires no linkage. After building it against a number of xulrunner headers, the plugin works fine in Opera.
Creating the header package
Considering the above, a simple npapi-sdk package is not enough. We at least need to install
libxul.pc satisfies configure checks on more packages but breaks VLC (as it tries to link with non-existent xulrunner libraries). If we hack the latter and remove
Libs: from it, VLC builds fine.
Right now, I’m testing a simple mozilla-plugin-sdk package. It installs the complete set of xulrunner headers along with the two forementioned pkg-config files, satisfying all Mozilla plugins I’ve tried. Sadly, due to number of headers the package is awfully large.
The next step would be probably stripping unnecessary headers out of the package. I already started using
makedepend to check which headers are actually used by Netscape plugins. Any further tips would be appreciated.