To me it seems very difficult to troubleshoot a XPCOM registration failure. That is, after carefully following all of the correct steps to register a new C++ XPCOM .so, an alert(Components.classes[myCID] ) displays "undefined". Also, the component shows up in the type library manifest (xpti.dat) but not in the component manifest (compreg.dat). Where should we start when trying to figure out what the problem is?
I'm merely trying to get Alex's sample to work with firefox 1.5 and Gecko SDK 1.8a2 on Linux: http://www.iosart.com/firefox/xpcom/ >From what I percieve, the registration process should, briefly, go like this: 1. Download and unpackage Alex's sample, Gecko SDK 1.8a2, and Firefox 1.5. 2. Use the xpti tool to generate a header file and a xpt file. Send the xpt to /[firefox-install]/components 3. Edit the makefile and build the sample. Send the .so to /[firefox-install]/components 4. Delete compreg.dat and xpti.dat from the Mozilla profile directory. 5. touch .autoreg back in [firefox-install] 6. Be sure that [firefox-install] in the LD_LIBRARY_PATH env variable 7. Go to gecko-sdk/bin and execute: regxpcom /[firefox-install]/components 8. Start firefox and test it. _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
