Hi there,

I recently ported my browser embedded app from mozilla0.9.0-based to
0.9.5-based. I downloaded the src tarball and built mozilla 0.9.5 release with
MOZ_PROFILE=1.
And then I compiled my app with its headers in its dist/include and linked
my app with its libs in dist/lib through VC++6 IDE setting.
However, I found that calling mozilla APIs from my app resulted in
calling wrong APIs at runtime. For example, when my app called on
document->GetScriptableGlobalObject, the system threw the assertion. I
then stepped into the assertion point and found InsertStyleSheetAt (in
nsDocument)
got called instead of GetScriptableGlobalObject. the system looked into wrong
APIs at runtime.
Such API calls was ok with 0.9.0 libraries.  I also tried with 0.9.3 and 0.9.4
build and they have the same problem.
It seems that the mozilla libraries linked into my app at compilation are
inconsistent
with the dlls at runtime. That is, the methods in the library for the
corresponding dll may have different
ordinal numbers from the dll somehow. I cleaned up my computer and rebuild
mozilla from
scratch but the problem remains. I have also made my app setting as consistent
as possibe with config/win32 file.
I'm just wondering if new build env has messed up with old stuff.
Does any tools have to be updated since 0.9.0 release? Could anyone give some
clues?


Thanks

begin:vcard 
n:;
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
note;quoted-printable:-------------=0D=0AThis e-mail is solely for the use of the intended recipient and may=0D=0Acontain information which is confidential or privileged. Unauthorised=0D=0Ause of its contents is prohibited. If you have received this e-mail in=0D=0Aerror, please notify the sender immediately via return e-mail and then=0D=0Adelete the original e-mail.
x-mozilla-cpt:;-2080
end:vcard

Reply via email to