Tor Lillqvist 93b1b381ed Don't build Python if DISABLE_PYTHON is TRUE ... I don't know if this is the right thing to do. The --disable-python switch is documented to "Disable build of Python 2.x UNO API". Does that mean that it should disable use of Python at run-time completely? What about use of Python tools at build-time, do we have such? Will --disable-python then disable their use, too?		2011-05-29 20:16:19 +03:00
..
prj	Merge commit 'ooo/DEV300_m103'	2011-03-23 16:59:29 +01:00
makefile.mk	Don't build Python if DISABLE_PYTHON is TRUE	2011-05-29 20:16:19 +03:00
Python-2.6.1-mingw.patch	CWS-TOOLING: integrate CWS mingwport22	2009-08-26 06:36:38 +00:00
Python-2.6.1-nohardlink.patch	Make the patch actually apply	2011-05-28 13:18:08 +03:00
Python-2.6.1-sysbase.patch	masterfix from: sb140: #i117456# on Solaris 11 against Solaris 10 baseline, trick python configure into thinking it sees Solaris 10	2011-03-18 17:31:51 +01:00
Python-2.6.1-urllib.patch	fixed urllib.urlopen in the internal python (fdo#31466)	2010-11-23 18:38:31 +01:00
Python-2.6.1-vc10.patch	Visual Studio 2010 project files for Python	2010-10-29 01:14:45 +02:00
Python-2.6.1.patch	Make debugging the Python interpreter simpler	2011-02-14 02:41:32 +02:00
Python-aix.patch	get this to build on AIX	2010-10-13 14:42:06 +01:00
Python-parallel-make.patch	ause126: #i114866# applied patch from issue: fix parallel build issue	2010-10-08 16:12:40 +02:00
Python-ssl.patch	Clean up Python patches a bit	2011-02-14 02:41:30 +02:00
pyversion.mk	Drop OS2	2011-05-21 16:38:28 +03:00