On 2016/12/14 10:29 AM, Jason Marshall wrote:
I have created a text file test script in compliance with your instructions and called 'cscript' by
directly defining
the script engine using the '/e:javascript' parameter. The call and output are as follows, but it
seems that despite
using the parameter, the same error arises as with the build:
Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript runtime error: Automation
server can't create object
I guess that this would imply an issue with my individual set-up, as it seems that the use of the
parameter that you and
Thorsten have identified would work in the majority of cases.
Would anybody know what may have prevented this from working?
Some googling around suggests that this has something to do with Internet Exploder security zones, but who knows exactly
what. The "fixes" are not great either, suggesting turning off various protections.
Honestly, unless you really __want__ to do windows specific development on LibreOffice, I would suggest running Linux
inside a VirtualBox VM on your Windows machine (or on another machine) and doing LibreOffice development there, where we
are more likely to be able to help you get a working setup.
Sorry about this, Windows is just not a very robust development platform (despite having lots of
nice tools available).
It's just waaaaay too easy to end up with a broken build environment for reasons completely outside
our control.
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.