odfstudio

Files

T

Tor Lillqvist c29098917a Get rid of (most uses of) GUI

GUI only takes values UNX or WNT, so it is fairly pointless. One can check
whether OS is WNT or not instead.

Change-Id: I78ae32c03536a496a563e5deeb0fca78aebf9c34
Reviewed-on: https://gerrit.libreoffice.org/1304
Reviewed-by: Peter Foley <pefoley2@verizon.net>
Tested-by: Peter Foley <pefoley2@verizon.net>

2012-12-25 17:53:25 +00:00

CLITest.java

…

makefile.mk

Get rid of (most uses of) GUI

2012-12-25 17:53:25 +00:00

readme.txt

…

readme.txt

This test is for Windows only!

The cli test uses .NET assemblies: 
cli_types.dll, 
cli_basetypes.dll, 
cli_ure.dll, 
cli_cppuhelper.dll.


When an office is properly installed then these assemblies can be found in the 
global assebly cache (GAC), for example in c:\windows\assembly.

When the test is run then the assemblies are used from the GAC. That is 
one has to make sure that one has the respective office installed.

The test can also be run without an installed office. Then the assemblies are used 
which reside next to the executable. The testtools project copies the assemblies from
the build environment into the wntmscixx\bin folder.

However, if for some reason an assembly remains in the GAC than it is used no matter 
what.


The qa test simply executes the cli_bridgetest_inprocess.exe. All console output is decarded.
When the test fails one should directly run that executable. Then one may see the cause 
of the failure in the console.