On Thu, 09 Apr 2009 10:55:18 -0500, Jan Holst Jensen
<[email protected]> wrote:
Alexandro Colorado wrote:
On Wed, 08 Apr 2009 16:31:52 -0500, Jan Holst Jensen
<[email protected]> wrote:
I have the final python code working on the command line on Linux,
where I interface to the shared library via ctypes in Python 2.5. But
my OpenOffice 3.0.1 on Windows runs a Python 2.3.4 that does not have
ctypes built-in :-/.
for a while we been trying to migrate OOo to Python 2.6, hopefully we
can count on your help to make sure that everything compiles including
ctypes.
Given that I will end up with a commercial add-in that will require
ctypes I would definitely welcome the Python upgrade as it would
simplify my deployment :-). I don't have any experience compiling
OpenOffice but I can help a little by testing pre-release builds and
check whether I see any issues in the little corner of the OOo API that
I rummage around in.
Has the Python 2.6 support reached a stage where I can test a build ? Is
it likely to be in 3.1 ?
Kind regards
-- Jan
Joerg Budischewski is currently working on the build as well as Eric
Bachard, they would be able to help you out getting the compiles in shape.
There is a tutorial on how to build OOo that would be helpful.
http://wiki.services.openoffice.org/wiki/Ooo-build
also helping us debug some of the Python misscompiles would be a good
idea. We also have a student working on this task under the Education
mailing list ([email protected]). You are also welcome to join
and share notes.
--
Alexandro Colorado
CoLeader of OpenOffice.org ES
http://es.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
