When compiling vlc-0.8.5-r4 with USE="nsplugin -seamonkey" it depends upon mozilla-firefox. However, it seems to place the plugins/components in /usr/lib/mozilla instead of /usr/lib/mozilla-firefox. I think this might be that mozilla-firefox is not the standard dir for mozilla plugins/components?
Anarchy, I'm not a Mozilla user you know, can you tell me where what and when?
Usually nsplugins (or symlinks to them) go to /usr/lib/nsbrowser/plugins so all compatible (mostly mozilla) browsers can see them. Maybe even seamonkey can use plugin built against firefox and vice versa, not sure. Installing them to /usr/lib/mozilla makes them visible only to former mozilla suite. Moving /usr/lib/mozilla/plugins/libvlcplugin.so into /usr/lib/nsbrowser/plugins made VLC appear in firefox's about:plugins. Not sure what to do about the /usr/lib/mozilla/components/vlcintf.xpt file, what it is for... netscape-flash places its .xpt file also in /usr/lib/nsbrowser/plugins so maybe it works that way...
In /usr/libexec/mozilla-launcher there is this for all programs: # Make sure netscape-compatible plugins are picked up [[ -z $MOZ_PLUGIN_PATH ]] && export MOZ_PLUGIN_PATH=/usr/lib/nsbrowser/plugins So putting all files in there should be a safe bet. Oh, Diego, and it should install libvlcplugin.so with the right permission (755 instead of 644).
Thanks you all for reporting, I just remembered that I used to have support for nsplugin before so I just gone looking for that and indeed I had to rewrite the plugin location. I'm currently build testing, will add -r4 later today (with also a couple more fixes).
Okay should be fixed now (in -r5), hopefully. Let me know if it's still a problem.
(In reply to comment #5) > Okay should be fixed now (in -r5), hopefully. Let me know if it's still a > problem. Works nicely, thanks.
