Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 17/12/11 21:33, Lars Callenbach wrote:
Hello,

I have a template for the quantlib addin which works for OO3.2.
Unfortunately it does not work for LibreOffice-3.4.

i'm not familiar with Calc addins, but in general UNO based extensions
are supposed to work with newer versions as well (unless using
unpublished APIs that actually are changed, which is AFAIK quite rare).

Does anybody have
a template with necessary interface functions in c++ for LO-3.4? I
have looked at the c++ examples in the SDK without success. Using the
ideas of the java examples did not work. At the moment the plugin
crashes LO if I try to insert a function.

that sounds like an LO bug; extensions are not supposed to crash LO;
please file in bugzilla and attach a backtrace if you can.

By the way: I have to
replace the onboard libstdc++ in ure-link/lib by the system libstdc++
to use other libraries. Why is there on old libstdc++?

i think by now it is mostly for historic reasons.
until 5 years ago or so g++ and libstdc++ regularly changed ABI, so OOo
could not rely on the needed version being available on Linux systems.
but now libstdc++ seems to be stable, so i guess we could get rid of it
in LO4 (it also causes problems with gdb python-fu).

i don't know where the bundled libstdc++ comes from and why it's outdated.

Help (and working code samples) would be appreciated.

Lars




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.