> But even after that, something else breaks in pyuno when building on
> Windows. Investigating.
I think I fixed it now, commit 6cb4b2e338d47943f29b6eee1d8cadca251c50f2 in
master of ure. Please verify that it still works as intended on Unix.
--tml
_
> Now, pyuno.so is symlinked to libpyuno.so.
This of course needed some conditionals, to be done only when $(DLLPRE) is
non-empty.
But even after that, something else breaks in pyuno when building on Windows.
Investigating.
--tml
___
LibreOffice ma
Hi Andreas,
On Sat, 2011-04-23 at 23:15 +0200, Andreas Becker wrote:
> I figured out that libpyuno.so is required for compilation, sorry for
> the confusion. Now, pyuno.so is symlinked to libpyuno.so.
So - I reviewed the patch; lots of nice cleanup in there - although,
it'd be great to se
Hi Andreas,
got around my problem by disabling translations.
Finally, I got it installed. Though, scp2 needs patching and Python
modules have even on Mac OS X .so endings stated here:
scp2/source/python/file_python.scp:303:// pyuno.so even on Mac OS X,
because it is a python module
Is t
Hi Hanno,
>[join('translate',filename) for filename in 'ChangeLog', 'COPYING',
> 'LICENSE', 'README'])]
> ^
> SyntaxError: invalid syntax
> dmake: Error code 1, while making './unxlngx6.pro/misc/build/so_built_trt
> '
>
> I did not sus
On Wed, 20 Apr 2011 17:53:20 +0200
Andreas Becker wrote:
> First of all, it has nothing to do with that patch.
> You should perhaps update automake (my version is 1.11).
You are so right. automake 1.11 does just fine.
Now then, I got this error:
=
Building module translate_toolkit
=
Hi Hanno,
First of all, it has nothing to do with that patch.
In configure.in, AM_PATH_PYTHON([2.2]) check is done. You can look into
aclocal.m4 line 205 ff. and try to debug.
You should perhaps update automake (my version is 1.11).
Maybe is works when you set $PYTHON=python before running autoge
Hi Andreas,
your patchset applies fine to 3.3.99.1. Though, configure fails with:
checking which python to use... external
checking for a Python interpreter with version >= 2.2... none
configure: error: no suitable Python interpreter found
I test with python3.1 as only version installed.
# pytho