|
Hi Everybody,
I went through all of the same issues that most
everybody here has talked about with FF .5 registration. My scenario was that I
developed a toolbar for FF 1.0.X and it has come time to upgrade this to work
with FF 1.5. It was my understanding that the Gecko 1.7 SDK would be sufficient
to use with FF 1.5. Not the case however. When I tried to instantiated my C++
component I received a NS_ERROR_XPC_CI_RETURNED_FAILURE error. I even went so
far as to create an empty shell of a component and still received the error. So
after mucking around for a day or so I decided to solicit the news group where I
learned that in fact we had to use the 1.8 Gecko SDK for FF 1.5. No problem I
thought - however I ran into several issues. One issue was that I no
longer could use nsEmbedString class as it would no longer compile. After
research I discovered that I should use nsString - however to use this class I
had to define MOZILLA_STRICT_API. So I said what the heck - so I defined out of
spite. So now everything compiles except for one tiny problem - I can no longer
use NS_GetServiceManager because it is not included when I define
MOZILLA_STRICT_API. My question is how can I get the global instance of the
Service Manager now? Is there another method to do this? Or should I be using a
different string solution instead of defining MOZILLA_STRICT_API?
Thanks for looking at this issue!
Tom -
|
- XPCOM component not getting registered in Firefox 1.5 Gautam Bhagra
- Re: XPCOM component not getting registered in Fir... Philippe C. Martin
- Re: XPCOM component not getting registered in Fir... Mook
- Re: XPCOM component not getting registered in... Christian Biesinger
- Re: XPCOM component not getting registered in... Gautam Bhagra
- Re: XPCOM component not getting registere... Christian Biesinger
- Re: XPCOM component not getting regis... Gautam Bhagra
- Re: XPCOM component not getting ... Christian Biesinger
- Re: XPCOM component not getting registered in Fir... Thomas Lee
- Re: XPCOM component not getting registered in... Christian Biesinger
- Re: XPCOM component not getting registered in... Thomas Lee
- Re: XPCOM component not getting registere... Martin Kremer
- Re: XPCOM component not getting regis... Christian Biesinger
