On Mon, Jul 17, 2006 at 06:50:55AM +0200, Mike Hommey wrote: > On Sun, Jul 16, 2006 at 10:25:47AM +0000, Michael Koch <[EMAIL PROTECTED]> > wrote: > > Package: libxul-dev > > Version: 1.8.0.4-2 > > Severity: important > > > > nsEmbedAPI.h declares NS_Embedding but no lib in xulrunner implements this > > function. > > Or I'm at least unable to find it. The problem with this is that > > Eclipse (SWT) needs this method to embed a gecko engine embedded. > > > > This method should either be implemented or completely removed. I would > > prefer to see the first but if its get removed what is the alternative > > to use? > > Mmmmm I did answer to that when you sent me a mail a few weeks ago, but > since your mail is @gmx.de i suspect it never ended in your mail box (I > often get bounces from there, but i'm getting so much fake or irrelevant > mailer daemon messages that i miss a lot of real ones :(
I have checked my mails again and I never got it. Damn GMX. > Here is what I wrote about the headers issue: > > Looking at the source code for xulrunner, it's intentional. The problem > is headers are not necessarily in sync with the fact that symbols are > hidden... I think the symbol definition in the header should be removed then. > And about the alternative: > You should patch the eclipse source to use NS_InitXPCOM3 or > NS_InitXPCOM2 instead, and that means you also have to add code for > components auto registration. Another option would be to look around if > a patch for eclipse exists to make it use javaxpcom instead of its own > xpcom stub. As of xulrunner 1.8.0.4-1, javaxpcom is not yet packaged, > but it is planned for 1.8.0.4-2. > If you opt for the first option and need help with embedding code, I > can give a hand. I'd personally prefer the second option. I think I opt for the first solution. It seems to be the less invasive for me. Upstream still builds against Mozilla 1.4 and this is no chance yet to make them support xulrunner. Thanks for your help. Michael -- http://www.worldforge.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
