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 /hunspell | |
| parent | Mac: actually use the define that is used in the patch, link against SDK (diff) | |
| download | core-93b1b381ed8567029cc077a818e5aff0b4ed1482.tar.gz core-93b1b381ed8567029cc077a818e5aff0b4ed1482.zip | |
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 'hunspell')
0 files changed, 0 insertions, 0 deletions