diff options
| author | Tor Lillqvist <tml@iki.fi> | 2011-05-27 20:58:57 +0300 |
|---|---|---|
| committer | Tor Lillqvist <tml@iki.fi> | 2011-05-29 20:16:19 +0300 |
| commit | 93b1b381ed8567029cc077a818e5aff0b4ed1482 (patch) | |
| tree | 0c4fb80e377ebb6494ebd38d65985143eb4df301 /python | |
| parent | 5c44a7e02f8d09c276ad0b22b80fed4826a1dfc6 (diff) | |
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?
Diffstat (limited to 'python')
| -rw-r--r-- | python/makefile.mk | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/python/makefile.mk b/python/makefile.mk index fb729bda8db5..f51e7e88398f 100644 --- a/python/makefile.mk +++ b/python/makefile.mk @@ -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 |