Re: Firebird - status update (not ready yet)

Noel Grandin <noelgrandin -AT- gmail.com>
Mon, 15 Aug 2016 08:57:04 +0200


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 ownright, and we're always going to be fighting fires if we keep trying to shoehorn it into a situation where it's not verycomfortable.


Just my 2c

Context

Firebird - status update (not ready yet) · Bunth Tamás
- Re: Firebird - status update (not ready yet) · Lionel Elie Mamane
  - Re: Firebird - status update (not ready yet) · Bunth Tamás
    - Re: Firebird - status update (not ready yet) · Lionel Elie Mamane
      - Re: Firebird - status update (not ready yet) · Bunth Tamás
        
        Re: Firebird - status update (not ready yet) · Noel Grandin
        
        Re: Firebird - status update (not ready yet) · Bunth Tamás
        
        Re: Firebird - status update (not ready yet) · Lionel Elie Mamane
        
        Re: Firebird - status update (not ready yet) · Rene Engelhard
        Re: Firebird - status update (not ready yet) · Lionel Elie Mamane

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.