Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a plugin, which works fine, when I link it with GeckoSDK 1.9.
Now I switched to using GeckoSDK 1.9.1.16, and it stopped getting detected on Linux (on Windows it still works fine) – about:plugins doesn’t show it any more!
There were no other changes, other than switching INCLUDE/LIB directories in the makefile, and renaming nppupp.h -> npfunctions.h.
I tested it with Firefox 3.5, 3.6 and 4.0 beta – the same result.
Any ideas?
Ok, in case anyone is interested, I’ll answer my own question.
It turns out they didn’t just rename npupp.h -> npfunctions.h, but rearranged the headers somehow.
As a result, npfunctions.h got included before XP_UNIX is defined (in prcpucfg.h), which in turn led to npentry functions (NP_GetMIMEDescription, etc) in my code getting defined without being previously declared, hence having C++ linkage, hence the browser couldn’t find it.
Hello Mozilla, what’s up with self-contained headers?