John Nason wrote: > Hi All, > I am running into binary compatibility problems with my plugin dlls built > against Moz1.0RC2 interfaces and run with NS7.0PR1. I was under the strong > impression that the new NS was spun off of MZ1RC2. I have updated my code > from my previous MZ9.4.1 NS6.2.X (which worked fine) and now I am getting > dll entry point not found errors for GetSharedBufferHandle. > I was thinking that maybe I am missing a flag that I should be building > with? I know for instance that there are debug flags that prevent inlining > of some string functions, which would result in a problem like this. Anyone > know if there are some specific flags that I need to be NS7.0 > compatible(like MOZ_DEBUG, NDEBUG, or something)? I have tried building > against debug and release builds of Moz1RC2 with various flag > combinations... works fine with Moz but no go with NS. Advice please? > Thanks a lot! > -john
John, What gave you the impression that all the interfaces in RC2 were frozen? I have repeated stated many many times that only interfaces marked with the FROZEN status tag will not change from release to release (build to build). Any interface not marked with such a tag must be considered experimental and subject to change without notice. See [1] for a list of frozen interfaces via lxr. For your specific problem there are two things to note. First, only building optimized will give you string and/or xpcom library that is reusable. See [2] for the tip of the iceberg bug for debug-reuse issues. (yes, we probably should start a meta tracking bug as there will be many issues that pop up.) Secondly, sorry to say, but prior to RC3, the abstract string classes were not frozen. (yes, we suck as many frozen interfaces using strings as parameters). So, my advice, rebuild against RC3 and forget about working in previous versions. The next version of the Netscape client should be compatible with mozilla RC3. Doug Turner [EMAIL PROTECTED] [1] http://lxr.mozilla.org/seamonkey/search?string=status+FROZEN [2] http://bugzilla.mozilla.org/show_bug.cgi?id=129959
