John Cebasek wrote: > We have a plugin and associated dylibs on Mac OS X that works with > Firefox 2, which now must be brought up Firefox 3. I've got the code > compiling, but I'm having a weird link error. Well, it's not that weird, > it's not finding a bunch of symbols. But where did they go? > > The (beginning) of the errors are as follows: > > __ZNK9nsAString12BeginReadingEv > __ZN9nsAString17DefaultComparatorEPKtS1_j > __ZNK9nsAString6EqualsERKS_PFiPKtS3_jE > __ZNK10nsACString12BeginReadingEv > /build_files/VizibleObjectModelImpl.build/Debug/VizibleObjectModel(STLport).build/Objects >
There are two versions of "nsAString". There is the internal, unstable version, and a frozen/stable version. It appears that you are (correctly) linking to the stable version, but are not linking against the necessary libraries. Please see http://developer.mozilla.org/en/docs/XPCOM_Glue You want the "Frozen linkage: dependent glue" strategy. > When I first compiled Firefox to build the dylibs, I just followed the > instructions on mozilla developer page. MinefieldDebug seems to work > just fine! > > Our build script just cd's to the mozilla directory and calls the make > -f client.mk build command. > > Here's our mozconfig: > > . $topsrcdir/browser/config/mozconfig > . $topsrcdir/build/macosx/universal/mozconfig ... > ac_add_options --with-macos-sdk=/Developer/SDKs/MacOSX10.4u.sdk > mk_add_options [EMAIL PROTECTED]@/../build > mk_add_options MOZ_MAKE_FLAGS="-j4" # use parallel make This is the only part of the mozconfig you should have. Please remove all the rest of the options, especially options such as --disable-libxul and --enable-xpcom-obsolete which cause fairly radical changes to the linking strategy used for the app. --BDS _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
