On Mon, Jan 23, 2012 at 09:07:13AM +0100, Stephan Bergmann wrote:
On 01/22/2012 11:02 PM, Lionel Elie Mamane wrote:
OTOH, even if we find a good way to handle "library load path"
issue, it still does not solve the problem of how the .oxt will
work with a LibreOffice compiled with --with-openldap, such as
e.g. Debian's one.
In the --with-openldap case, postgresql-sdbc-impl.uno.so contained
in the postgresql-sdbc oxt links against some other lib than
libldap50.so?
Yes, because in that case there is no libldap50.so; the OpenLDAP
library is called something like libldap{,_r}-2.4.so.2 (these are the
names on my system; I guess the _r version is the
thread-safe/reentrant one).
On Mon, Jan 23, 2012 at 09:26:08AM +0100, Stephan Bergmann wrote:
On 01/23/2012 09:07 AM, Stephan Bergmann wrote:
One more reason to change it from an extension into a proper part
of LO, I would say.
Lionel, what do you think about changing the extension into an
integral part of LO 3.5? It should make all problems go away (on
all platforms; at least so I would think). I could offer you to do
the change, or land you a hand if you want to do it yourself.
Users loose the feature to use a newer PostgreSQL-SDBC with an older
LibreOffice. But Fridrich and you agree it fixes all our issues, so
OK, I consent to it. I'm happy to let you and/or Fridrich do the
change.
--
Lionel
Context
Re: [Libreoffice] rpath / ... for extensions (and the case of PostgreSQL-SDBC) · Stephan Bergmann
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.