Simon Hausmann fecefdd369 Fix mapping of features to private features ... When a feature generates a private feature, we should not just repeat the condition but also make it depend on the original feature. In qmake features had different outputs, while we have a 1:1 mapping. For example the developer_build feature had "private_tests" as an output feature. There's no condition attached to the feature and auto-detect is off, so we'd generate qt_feature("developer_build" AUTODETECT OFF) qt_feature("private_tests" AUTODETECT OFF) and that's wrong, because when the user enables the visible feature (developer_build) we want it to propagate to the private_tests feature. Change-Id: Id8408864802fa1e1ed9e67a5f47d1d2fde38d321 Reviewed-by: Leander Beernaert <leander.beernaert@qt.io> Reviewed-by: Qt CMake Build Bot Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2019-07-22 08:29:33 +00:00
..
tests	Enable recursive expansion of simple qmake variables	2019-07-18 07:26:01 +00:00
cmakeconversionrate.py
configurejson2cmake.py	Fix mapping of features to private features	2019-07-22 08:29:33 +00:00
generate_module_map.sh
helper.py	Add support for QML plugins	2019-07-15 12:28:12 +00:00
json_parser.py	Improve configurejson2cmake.py to handle non-compliant qmake JSON	2019-05-27 07:48:51 +00:00
Pipfile
pro2cmake.py	Add special case handling for corelib mimetypes resources	2019-07-18 08:05:58 +00:00
pro_conversion_rate.py
run_pro2cmake.py	Improve run_pro2cmake.py	2019-06-05 07:41:46 +00:00
special_case_helper.py	Improve special case handler to work on Windows	2019-06-11 14:09:54 +00:00