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?
This commit is contained in:
@@ -33,6 +33,9 @@ TARGET=so_python
|
||||
# --- Settings -----------------------------------------------------
|
||||
|
||||
.INCLUDE : settings.mk
|
||||
|
||||
.IF "$(DISABLE_PYTHON)"!="TRUE"
|
||||
|
||||
.INCLUDE : pyversion.mk
|
||||
|
||||
.IF "$(SYSTEM_PYTHON)" == "YES"
|
||||
@@ -146,7 +149,9 @@ PYVERSIONFILE=$(MISC)$/pyversion.mk
|
||||
|
||||
|
||||
.INCLUDE : set_ext.mk
|
||||
.ENDIF # DISABLE_PYTHON != TRUE
|
||||
.INCLUDE : target.mk
|
||||
.IF "$(DISABLE_PYTHON)"!="TRUE"
|
||||
.INCLUDE : tg_ext.mk
|
||||
|
||||
.IF "$(L10N_framework)"==""
|
||||
@@ -182,3 +187,4 @@ $(PYVERSIONFILE) : pyversion.mk $(PACKAGE_DIR)$/$(PREDELIVER_FLAG_FILE)
|
||||
-rm -f $@
|
||||
cat $? > $@
|
||||
|
||||
.ENDIF # DISABLE_PYTHON != TRUE
|
||||
|
Reference in New Issue
Block a user