On 15 August 2016 at 08:57, Noel Grandin <noelgrandin@gmail.com> wrote:
Just a random thought - it seems like linking firebird into LO is a lot of
pain.
Is there any real downside to just building firebird as an executable and
then running it as a sub-process of LO?
The difficulty I run into is actually that there are now two libraries
of firebird,
and they are linked against each other. So the pain would be still
there I think,
if we'd make a sub-process (or it would be even worse,
since we'd need the runnable firebird file too).
But with Lionel's help things seem to turn good now.
Tamás
On 15 August 2016 at 08:57, Noel Grandin <noelgrandin@gmail.com> wrote:
Just a random thought - it seems like linking firebird into LO is a lot of
pain.
Is there any real downside to just building firebird as an executable and
then running it as a sub-process of LO?
It just seems to me that we're running "against the grain" here - firebird
is a large complex application in it's own right, and we're always going to
be fighting fires if we keep trying to shoehorn it into a situation where
it's not very comfortable.
Just my 2c
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.