Apache OpenOffice (AOO) Bugzilla – Issue 11753
Adding python scripting language to the external project
Last modified: 2003-07-31 09:24:17 UTC
Hi, I want to add a python-uno bridge module to the CVS repository within the UDK-project. This project needs the 3rdparty code python as a prerequisite. The makefiles to build the python core should be checked into the external project. I have filled out the form for 3rd party code (see http://external.openoffice.org), however I am unable to send it to so-external@sun.com, I would like to ask mh to forward it to this location. Product Name : Python Product Version : 2.2.2 Vendor or Owner Name : Python Software Foundation Vendor or Owner Contact : psf@python.org OpenOffice.org Contact : jbu@openoffice.org Date of First Use / date of License : 2001 URL for Product Information : http://www.python.org URL for License : http://www.python.org/2.2.2/license.html Purpose : I want to introduce the scripting language python into the OOo build environment, because it is needed as a prerequisite for the pyuno module in the UDK project. Type of Encryption : none Binary or Source Code : source I have discussed with kso and st, that in the first run, only the makefiles for building python will be checked in. As the two projects shall not be built by default, the source tarball is not checked in for now, but may follow later. For further information about pyuno, please see http://www.budischewski.com/pyuno/python-bridge.html and the dev@udk.openoffice.org mailing list from the end of january up to now. I will attach the python project to this issue within the next days.
Hi Martin, do we really need the agreement of Sun Legal for python, even when we don't check in the tar-ball, just additonal makefiles into external/python ? If yes, do you have a rough estimation, how long this will take (Some people are interested to get to know, when it is available in CVS repository).
Hi Martin, have you seen my last comment (2003-03-05) ? Any remarks ?
Created attachment 5209 [details] The python module as it should be checked in
hi joerg, kai, do we plan to integrate this bridge into the normal OOo build ? In this case we would have another prerequite for building OOo. If we only want to build this additionaly (with add. download of external phython) I see no reason why not to commit makefile/d.lst/build.lst into udk project (as long as they should be dual liecensed).
If the udk project owners agree, it may at some time in future become part of the official build, currently it is not. As this separation is IMHO sensible and we have this separation already, why shouldn't we do it the correct way from the beginning ?
Hi again, thinking about it a second time, I definitly want to build python within a module different from pyuno, because the headers and shared libs should be delivered to the global environment. (Otherwise it becomes difficult to compile/link pyuno components). So if you don't want to have python module in the external project, I would vote for a udk/python module. Kai, maybe you can find an agreement with Martin ?
I talked with Kai about this plan: * make pyuno available for a non default optional module in the OOo installation set. - document phython as a build requirement - build and deliver pyuno on regular basis - enhance scp to include pyuno in OOo installation set. i start preparing this on the ooo20030412 cws. - if build is available latest with beta2 we have to discuss, if we really need to include Runtime into installset or not. if not, we do not have the requirement for external/phython. nonetheless we also can start getting approval for external/phython now.
Hi, this sounds to be a promising start for a full python installation. At least for gcc builds, external/python is inevitable, as the python executable itself gets dynamically linked to the system's libstdc++.so.* . As pyuno needs the core uno c++ libraries within the python process, we definitly need a python executable linked with the office libstdc++.so. I will prepare such an installation set (with python runtime) with patches for scp. I hope to have this ready next week. Which files do I have to create patches for in order to change - document phython as a build requirement - build and deliver pyuno on regular basis ? When I have question about scp integration, I will put them to dev@installation.openoffice.org. Thx, Joerg
Created attachment 5494 [details] module to build python itself, now with configure-ppc patch
Created attachment 5495 [details] pyuno added to the scp project (new directory with new files)
Created attachment 5496 [details] patches to existing files in the scp project for adding pyuno
Created attachment 5497 [details] patches to pkgchk to allow python components to be deployed with uno packages
Created attachment 5498 [details] A samplepackage containing a java,native and python component, needed to check the pyuno installation check.
Hi Martin, please follow this steps to create an installation set with pyuno * add the following to lines to the environment script: (where can I add this in the configure process ?) unx: setenv PYTHONPATH .:"$SOLARVER"/"$UPD"/"$INPATH"/lib/python:"$SOLARVER"/"$UPD"/"$INPATH"/lib/python:"$SOLARVER"/"$UPD"/"$INPATH"/lib/python/lib-dynload setenv PYTHONHOME "$SOLARVER"/"$UPD"/"$INPATH" win: set PYTHONPATH=.;%SOLARVER%\%UPD%\%INPATH%\lib\python;%SOLARVER%\%UPD%\%INPATH%\lib\python:%SOLARVER%\%UPD%\%INPATH%\lib\python\lib-dynload set PYTHONHOME=%SOLARVER%\%UPD%\%INPATH% * use the python module from latest attachment of python.zip in this issue. Download http://www.python.org/ftp/python/2.2.2/Python-2.2.2.tgz and copy it as Python-2.2.2.tar.gz into the download directory of the python module. * checkout pyuno toplevel (a must !) * apply the scp.patch file attached to this issue extract scp.zip from within the scp module. It will inflate the following files source/python/makefile.mk source/python/python.scp source/python/unxbasic_python.scp source/python/winbasic_python.scp * apply the pkgchk_packages.cxx.patch to desktop/source/pkgchk/pkgchk_packages.cxx file ( you should get the approval for this patch from DBO and KSO, I will inform them separately ) * Build the projects (python and pyuno should be build one after another, rest can be built in parallel). * After building an installation set, you should have a PyUNO bridge package in the optional components tree in the setup package selection. * you can check your installation by doing the following: (see samplepackage.zip attachment) cd <office-install>/program ./pkgchk samplepackage.zip ./soffice "-accept=socket,host=localhost,port=2002;urp;" ./python <path-to-projects>/OO1.1Beta/pyuno/demo/swritercompclient.py You shouldn't get any error messages. * let me know, what is to be done next. Thx, Joerg
waiting approval for desktop/source/pkgchk/pkgchk_packages.cxx, reset prio.
jbu->mh: When you expect me to do something more for this issue, please speeak up, I currently assume that I delivered everything needed from my side.
I have created a followup issue #i14846# to stop confusion on too many already outdated patches.
I have created a followup issue #i14846# to stop confusion on too many already outdated patches. *** This issue has been marked as a duplicate of 14846 ***
closing fixed issues for 1.1. release.