Alexandru Croitor 2389aaf8c7 pro2cmake: Handle qmake condition operator precedence ... Unfortunately qmake does not have operator precedence in conditions, and each sub-expression is simply evaluated left to right. So c1|c2:c3 is evaluated as (c1|c2):c3 and not c1|(c2:c3). To handle that in pro2cmake, wrap each condition sub-expression in parentheses. It's ugly, but there doesn't seem to be another way of handling it, because SymPy uses Python operator precedence for condition operators, and it's not possible to change the precendece. Fixes: QTBUG-78929 Change-Id: I6ab767c4243e3f2d0fea1c36cd004409faba3a53 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2022-02-28 15:41:11 +01:00
..
data	pro2cmake: Handle qmake condition operator precedence	2022-02-28 15:41:11 +01:00
__init__.py
test_lc_fixup.py	cmake scripts: move parser into separate file	2019-10-10 13:35:43 +00:00
test_logic_mapping.py	Remove conditioning on Android embedded	2021-09-17 17:30:14 +02:00
test_operations.py	CMake: Fix test_operations	2019-05-17 13:26:26 +00:00
test_parsing.py	pro2cmake: Handle qmake condition operator precedence	2022-02-28 15:41:11 +01:00
test_scope_handling.py	pro2cmake: Fix test_scope_handling.py	2022-02-28 15:40:36 +01:00