Hi,
On Mon, Jun 24, 2013 at 12:31:22PM +0300, Andres Gomez wrote:
On Mon, 2013-06-24 at 11:25 +0200, Rene Engelhard wrote:
Hi,
On Mon, Jun 24, 2013 at 12:18:06PM +0300, Andres Gomez wrote:
On Thu, 2013-06-20 at 20:20 +0200, Michael Stahl wrote:
...
The firebird specific libraries (fb builds its own versions
libicuuc/libicudata/etc.) are currently in install/program/firebird/lib
really? it bundles its own ICU? argh... can you teach it to use the
LO's ICU instead? no reason why we'd need to ship 2 sets of ICU libraries.
...
As I was writing in the wiki:
https://wiki.documentfoundation.org/index.php?title=Development/Base/FirebirdSQL#Compilation
We may hit some problems if we use LO's or systems ICU with the table
indexes.
I think the safest would actually be to use always FB's internal ICU
copy but other possible approaches are possible in order to face this
problem.
I think you are thinking too short.
Nnote that most distros will simply build with
system-firebird. (and whatever THAT one is built against - looks
like that it's *external* ICU here:
http://packages.debian.org/sid/libfbembed2.5)
...
That's why in the initial discussions we were already talking about
removing the possibility of "system-firebird" and always using an
internal compilation:
https://wiki.documentfoundation.org/index.php?title=Development/Base/FirebirdSQL#Compilation
http://firebird.1100200.n4.nabble.com/Firebird-as-backend-in-LibreOffice-td4633330.html
If this is the current option, could we please consider the possibility
to drop the whole idea and just stay with hsqldb? With my distro hat on,
I do not see any improvement with having to bundle hsqldb vs. having to
bundle firebird.
D.
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.