Hi all,
I trying to build the following C++ macro example.
http://api.libreoffice.org/examples/cpp/DocumentLoader/
But i get the following error:
# make
--------------------------------------------------------------------------------
The example loads the "test.odt" document in the DocumentLoader example
directory.
If you want to load your own document, please use:
DocumentLoader
-env:URE_MORE_TYPES="/usr/lib/libreoffice/ure-link/share/misc/types.rdb"
"filename" [connection_url]
-
Use the following command to execute the example!
-
make DocumentLoader.run
-
NOTE: This example does not use the new UNO bootstrap mechanism, it uses
still a socket
connection. The example use the
defaultBootstrap_InitialComponentContext method and provides
the additional office types via the UNO environment variable
-env:URE_MORE_TYPES=...
Before you can run this example you have to start your office in
listening mode.
-
soffice
"--accept=socket,host=localhost,port=2083;urp;StarOffice.ServiceManager"
--------------------------------------------------------------------------------
# make DocumentLoader.run
cd /usr/lib/libreoffice/sdk/LINUXexample.out/bin && DocumentLoader
-env:URE_MORE_TYPES=file://"/types/offapi.rdb"
"/usr/lib/libreoffice/sdk/test.odt"
/bin/sh: 1: DocumentLoader: not found
Makefile:101: recipe for target 'DocumentLoader.run' failed
make: *** [DocumentLoader.run] Error 127
Any hints?
Thanks in advance,
Aitor.
Context
- C++ Macro example: DocumentLoader · aitor_czr
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.