--enable-standalone-modules=xpcom,plugin

Hello all,

A long, long time ago (2 years?) someone ported VLC media players 
(http://www.videolan.org/vlc) mozilla module to OS X. Developement on 
this never really continued, basically because compiling the entire 
Mozilla tree just to build a plugin on OS X was getting annoying quite 
fast (and there was also a problem with video, but this has been 
corrected since).

Now that I have my new (faster) Mac, i thought i'd give it a shot again. 
  Compiling the entire mozilla tree is still annoying, but i'd thought 
I'd give it a try again. Compiling the entire mozilla tree (though it 
works) is annoying, because every developer would have to do it and it 
just takes hours which ppl don't want to spent waiting. Also because of 
our selfcontained "ports" like system for 3rd party dependencies, our 
nightlies would now take an extra 5 hours to finish. There is still no 
gecko-sdk for OSX, but i was thinking that i'd might try creating a 
minimal mozilla setup instead, that would be suited for linking mozilla 
plugins to.

Did some looking around and figured that 
--enable-standalone-modules=xpcom would be something useful for me. 
Tried it with 1.7.5 and built just fine. I soon realized though, I also 
needed plugin to be built. And this is where stuff goes wrong. On 
everything from 1.6 trough 1.8b1 i get builderrors with this configure 
line (--enable-standalone-modules=xpcom,plugin). Most often because it 
wants to link to libmozreg_s.a.
I tried adding libreg to the modules list, but this adds a slew of other 
stuff which I probably won't need (and besides it doesn't build as 
standalone either).


http://sidequest.org/weblog/archives/2005/03/mozilla_plugin.html

Anyone got any other ideas on what i can try?
DJ