If you only linked against xpcom.lib, then you cannot use nsMemory::
methods. That would explain the problem for sure. If you want to use
that function, then you must link against the glue. Unfortunately,
the xpcom glue for Gecko 1.7.x is horribly broken. It's practically
useless. I suggest that you instead continue using only xpcom.lib.
In place of nsMemory:: methods use the following:
NS_GetMemoryManager
nsIMemory::Alloc
I recommend that you verify that you are only linking to frozen
symbols from xpcom.lib. Use dumpbin /imports yourcomponent.dll to
determine what you are importing.
This document has recently been updated with more information about frozen APIs:
http://developer.mozilla.org/en/docs/XPCOM_API_Reference
You should make sure that your component only imports C-style
functions with extern "C" linkage. If you see any C++ name mangled
imports coming from xpcom.lib, then you are doing something wrong.
-Darin
On 5/5/06, Myles <[EMAIL PROTECTED]> wrote:
Clarifications:
When I say "Firefox 1.5 cannot find the method/function" I mean that the
script gets a type error that it is not a function.
I have tried linking against xpcomglue.lib or xpcomglue_s.lib, separately.
I'm building with Visual Studio 7.1.NET.
Myles
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
