examples to manage docs using LibreOffice as a major component

nicholas ferguson nicholasferguson at wingarch.com
Tue Sep 30 11:57:43 PDT 2014

I didn't understand your answer.  I think you said you would not give me the
samples of turning a cppunit test into a standalone executable ..because you
find me unskilled and I would then ask too many questions....  Is it your

And that first you want to see some contributions from me, to the
LibreOffice code base.... patches...

If I missunderstood your things... can you then tar up an example and send
it to me.


-----Original Message-----
From: LibreOffice [mailto:libreoffice-bounces at lists.freedesktop.org] On
Behalf Of Michael Meeks
Sent: Tuesday, September 30, 2014 2:54 PM
To: nicholas ferguson
Cc: 'libreoffice-dev'; 'Tor Lillqvist'
Subject: Re: examples to manage docs using LibreOffice as a major component

Hi Nicholas,

On Tue, 2014-09-30 at 13:43 -0400, nicholas ferguson wrote:
> >> you will need to solve a truck-load of bootstrapping issues
> Wow.  So in the past seven years, not a single successful attempt

	There are several successful attempts. It is certainly not
impossible to do this. Those attempts have however been done by people
skilled and experienced in the art of wrestling the LibreOffice octopus -
I've personally broken the back of a couple of them. My concern here is not
feasibility in the abstract, only the danger of yet more noisy and
time-consuming remote debugging by mailing-list to no useful purpose - ie.
ending up with something that is not contributed back.

>  at transforming a unit test.. and spinning it off into a separate 
> executable...a unit test like filters_test.cxx

	Sure - those unit tests run under cppunittester - a separate
executable; as you can see if you read the make output and/or read the
Makefiles ;-) Separately, if you use LibreOfficeKit (under Linux) you can
write your own separate executable (eg. gtktiledviewer) really extremely
easily - though you are limited by the currently exposed API there; failing
that you can link the code into an Android or iOS binary for yet another
incarnation. All of it is do-able (with some hard work).

> Hard to believe....  These unit tests have so much functionality 
> exposed... some hacker would seem to be naturally attracted to 
> transform them into an independent executable.

	They are already executed as shared libraries loaded into a separate
executable post compilation. That however happens inside the warm,
nurturing, and rather painfully constructed context of a live LibreOffice
build tree.

	But of course - as with -any- community / code problem - you are by
far more than welcome to contribute to fixing the situation and meeting your
own need. Indeed, I encourage you to get stuck into fixing whatever
perceived gaps there are, all of us are responsible for improving things
here as their means allow :-) I look forward to your patches.



 michael.meeks at collabora.com  <><, Pseudo Engineer, itinerant idiot

LibreOffice mailing list
LibreOffice at lists.freedesktop.org

More information about the LibreOffice mailing list