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


Browsing configure.in, I see three different binary options for various aspects of Pyhon "support":

--disable-python. "Disable build of Python 2.x UNO API"
--enable-ext-scripting-python. "Enables support for scripts in Python"
--with-system-python. "Use Python already on system"

Now, I am sure that in practice all combinations of these options don't work; do we really want and 
need so much optionality for Python?

The above options propagate into various autoconf variables that then are propagated into the build 
environment through set_soenv.in: 

BUILD_TYPE="$BUILD_TYPE PYUNO"
AC_SUBST(DISABLE_PYTHON)
BUILD_TYPE="$BUILD_TYPE PYTHON"
AC_SUBST(SYSTEM_PYTHON)
SCPDEFS="$SCPDEFS -DWITHOUT_EXTENSION_SCRIPTING_PYTHON"
AC_SUBST(ENABLE_SCRIPTING_PYTHON)

--tml



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.