summaryrefslogtreecommitdiffstats
path: root/mkspecs/linux-g++-32/qplatformdefs.h
diff options
context:
space:
mode:
authorAlexander Golubev <fatzer2@gmail.com>2024-03-07 22:26:26 +0300
committerAlexander Golubev <fatzer2@gmail.com>2024-03-07 23:36:18 +0300
commitfad4acbe084403340bb0ee6979ea18db464e7085 (patch)
tree557268e108f03e554cde0b12f1f49569344bc761 /mkspecs/linux-g++-32/qplatformdefs.h
parentbeb37238fa751dada93695a8b9ce1bb73aea1253 (diff)
downloadtqt3-fad4acbe084403340bb0ee6979ea18db464e7085.tar.gz
tqt3-fad4acbe084403340bb0ee6979ea18db464e7085.zip
Fix compilation with -disable-inputmethod and -no-inputmethod
As for now here are two sets of inputmethod options: - -enable-inputmethod/disable-inputmethod - which seems to supposed to control whether build the 'inputmethod' module or not - -inputmethod/-no-inputmethod - which seems to supposed to enable/disable inputmethod support without changing the ABI. Before the patch both -disable-inputmethod and -no-inputmethod were just breaking the build: -no-inputmethod were disabling some code with support for the module, but didn't disabled the module build itself nor build of plugins. -disable-inputmethod were disabling build of plugins and module, but didn't disabled code depending upon it. It seems the inputmethod support were still WIP when the last release of Qt3 came to be, hence the mess. This patch fixes the build if both -disable-inputmethod AND -no-inputmethod are supplied. Disabling only one is not enough due to tqmake/configure have problems handling two different options of the same name. Later the -inputmethod/-no-inputmethod should be probably removed entirely. Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
Diffstat (limited to 'mkspecs/linux-g++-32/qplatformdefs.h')
0 files changed, 0 insertions, 0 deletions