I'll take these. First off, none of these options are commonly used at all, and not part of our release testing (at least not yet) - they are basically unsupported for all intensive purposes. LIBXML2 support will be working in the next support, as will STL and internal plugins.
> It won't compile at all with standards-enforcing compilers (void * vs. > const void * issue, fixed by attachment #1). > > It doesn't compile with ABI_OPT_LIBXML2 because it looks for the include > > files in the wrong place (namely in libxml1's place). Fixed by > attachment > #2. This has since been fixed. Our libxml2 support in < 0.9.5 (i.e. CVS Head) just doesn't work. Be warned. > In function `abi_plugin_register': > ie_exp_Applix.o(.text+0x0): multiple definition of `abi_plugin_register' ... Abi works fine with externally built plugins, we just haven't updated our makefiles to build our existing sources as plugins yet in an XP manner. Short story is that you don't need to compile with ENABLE_PLUGINS set to enable plugin support in Abi. Dom
