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


On 01/06/2012 02:24 PM, Tor Lillqvist wrote:
Still, what prevents us from saying that a particular build of this
"extension" as shipped with LO x.y, works only with LO x.y?

OOo has a OpenOffice.org-maximal-version dependency for that; would need to replicate that as LibreOffice-maximal-version (in addition to the existing LibreOffice-minimal-version).

Another problem is how .oxt libraries find the internal LO libraries:

* On Linux, the .oxt library's RPATH would need to include the relative path from the .oxt location to the program/ directory. A dirty hack would be to hard-code the ../../.. length of the path from bundled .oxts to program/, and demand that such extensions can only be installed bundled (not user or shared).

* On Mac OS X, a similar hack with @loader_path would be needed (referencing relative to @executable_path would not work, as .oxt libraries are also loaded via uno executable from URE layer).

* On Windows, default library search order (next to executable) makes this a non-issue for soffice.bin, but still would cause problems with the uno executable.

Stephan

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.