Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 01/05/13 23:33, David Ostrovsky wrote:
On 30.04.2013 23:46, Stephan Bergmann wrote:
On 04/29/2013 11:42 PM, David Ostrovsky wrote:
cli_ure is failing to compile here atm.

How's it failing for you exactly?  I'd hope it does work now, across 
various Windows build configurations.

yes, after you've fixed it ;-) so, with this patch 
https://gerrit.libreoffice.org/#/c/3728/1
unit tests are invoked now on windows, but python is failing to locate 
the tests:

ImportError: No module named 'get_expression'

that's because the PYTHONPATH was not extended:

PYTHONPATH="$S/instdir/wntmsci13.pro/program/python-core-3.3.0/lib;$S/instdir/wntmsci13.pro/program/python-core-3.3.0/lib/lib-dynload:$S/instdir/wntmsci13.pro/program"

as expected with this function (PythonTest.mk):

# gb_PythonTest_add_modules directory module(s)
define gb_PythonTest_add_modules
$(call gb_PythonTest_get_target,$(1)) : PYPATH := $$(PYPATH):$(2)
[...]

And i don't see why ;-(

problem is the ":", on Windows it should be ";"... the CLASSPATH stuff
in the java makefiles has the same problem, there is some variable there
for the separator that should fix that.

by the way if the test fails to create a document the first thing you
should check in the debugger is if the process has 2 tklo.dll loaded
(that's what happened last time i tried and it definitely doesn't work).




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.