I'm building a C++ XPCom object. The object is intended to be a scriptable object meaning that it supports scriptable interfaces.

The module containing the body of the object (libxxx.so) is compiled, copied to the /components folder and regxpcom has been called. But creating, in JS, an instance of the object, fails. Also, the component doesn't show up in the "XPCOM Component Viewer".

Is there a checklist of "tests" that one can perform to know that their .so file is a valid (or not valid) vis-a-vis XPCOM? How do I debug this? Is the idea that I'm supposed to attach to the regxpcom process during registration (regxpcom) and trace the failure? Or is there an easier way to validate a .so file?

Thanks for any help.
Confused (and yes, sleepless) in Seattle

_______________________________________________
Mozilla-xpcom mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-xpcom

Reply via email to