User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release) Build ID: 20130514181517 Steps to reproduce: Since Firefox 22 there is no xpcom.dll in it. Thus my extension's XPCOM dll can't be loaded by Firefox and my extension does not work.
xpcom.dll is gone, and not used anymore (obviously) How are you building your extension? Supposedly, to build one for ff22, you need to use the corresponding SDK, which doesn't come with xpcom.dll either. So how are you building a ff22 extension that needs xpcom.dll?
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
I get HUNDERDS of compiler errors when trying to compile it using xulrunner 22 SDK. I event do not know how to resolve them. THANKS for such a great programming.
NS_OUTPARAM is nowhere defined also.
You should try getting on irc, in the #introduction channel.
OK, I've managed to compile it. However, it's not very good that now I need to have 2 idl files instead of one, need to have some patches for my code which allows me to not keep 2 separate copies of my binary component... Not good that compatibility with previous versions of SDK is not full.
I don't see why you'd need two idl files. As for binary components, you already needed a new binary component for each new version of Firefox.
New IDL compiler (based on Python - header.py) - don't know PRUint32 type anymore. It was replaced by new uint32_t type. Old compiler - does not know uint32_t type. That is why I need to have 2 IDL files.
PRUint32 vs. uint32_t changed in Firefox 17. Are you still trying to build a binary component for Firefox < 17?
You need to log in before you can comment on or make changes to this bug.