Hi Bernie,

I built mozilla 0.9.4 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. I had the same thought about the wrong
binary image resulted from wrong header info and thus checked my setting in
the IDE a few times. Actually, I tried with 0.9.3 before 0.9.4 and I tested
my app with 0.9.5 build just before and the similar problems occur across
these versions. The 0.9.0 is the only version is ok. Is any special setting
required in the DOS env when building the mozilla release libraries since
version 0.9.0?


Thanks

Chris



Bernie Maier wrote:

> Chris Shen wrote:
>
> > Hi there,
> >
> > I recently ported my browser embedded app from mozilla0.9.0-based to
> > 0.9.4-based. I built the release with debug info.
> > However, I found that calling mozilla APIs from my app resulted in
> > calling wrong APIs. For example, when my app called on
> > document->GetScriptableGlobalObject, the system threw the assertion. I
> > then stepped into the breakpoint and found
> > InsertStyleSheetAt (in nsDocument) got called instead of
> > document->GetScriptableGlobalObject. It seems to me that
> > the system looked into wrong APIs at runtime. Such API calls was ok with
> > 0.9.0 libraries. Did anyone have such porting problem before?
>
> Excuse me if I'm stating the obvious here, but this sounds like a classic
> header file mismatch problem.  When you say you built the release, did you
> mean you built the release of your app, or you built the Mozilla release?
> I think you need to rebuild your app with the new 0.9.4 header files.
>
> Cheers,
>
>      Bernie
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