I think what Eike suggests is to use guistdio.exe (perhaps rename it
appropriately, to something like soffice.com), and use _that_ when
calling soffice from the command line.
If I recall correctly from when I a long time ago had a look, Windows
nowadays (well, since XP at least) has APIs that make whatever tricks it
was that the guistdio program had to do as a separate process unnecessary.
It is more than enough to have soffice.exe and soffice.bin. (Could we at
some stage please rename soffice.bin to something with a normal .exe file
name extension? That would be no API break, would it?)
--tml
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.