History

Alexandru Croitor 6f5b1dd9ab pro2cmake: Handle WINDOWS_SDK_VERSION and simplifications Add custom code to handle WINDOWS_SDK_VERSION comparisons, similar to how it was done for QT_GCC_MAJOR_VERSION. Also fix simplify_condition to do mapping of conditions to unified tokens, similar how it was done for target conditions, so that the simplification process does not fail because of whitespace. Change-Id: Ia0cec6e1ffeed4c7859bb2a44423d0160222f425 Reviewed-by: Qt CMake Build Bot Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>		2019-09-27 08:43:16 +00:00
..
tests	Add support for converting qtTargetLibrary() value assignments	2019-08-08 13:03:28 +00:00
cmakeconversionrate.py	Improve styling of util/cmake scripts	2019-09-18 12:00:26 +00:00
configurejson2cmake.py	configurejson2cmake: Generate label for out-of-line tests	2019-09-24 09:57:10 +00:00
generate_module_map.sh	Begin port of qtbase to CMake	2018-11-01 11:48:46 +00:00
helper.py	cmake: Add BlueZ to the list of libraries used by Qt (connectivity)	2019-09-25 12:08:54 +00:00
json_parser.py	Improve styling of util/cmake scripts	2019-09-18 12:00:26 +00:00
Pipfile	CMake: pro2cmake.py: Simplify conditions	2019-01-29 09:29:38 +00:00
pro2cmake.py	pro2cmake: Handle WINDOWS_SDK_VERSION and simplifications	2019-09-27 08:43:16 +00:00
pro_conversion_rate.py	Adapt string formatting in util/cmake	2019-09-21 15:48:40 +00:00
README.md	Improve styling of util/cmake scripts	2019-09-18 12:00:26 +00:00
requirements.txt	Improve styling of util/cmake scripts	2019-09-18 12:00:26 +00:00
run_pro2cmake.py	Fix run_pro2cmake only_qtbase_main_modules option	2019-09-27 08:42:42 +00:00
special_case_helper.py	Improve styling of util/cmake scripts	2019-09-18 12:00:26 +00:00

README.md

CMake Utils

This directory holds scripts to help the porting process from qmake to cmake for Qt6.

Requirements

Python 3.7,
pipenv or pip to manage the modules.

Python modules

Since Python has many ways of handling projects, you have a couple of options to install the dependencies of the scripts:

Using `pipenv`

The dependencies are specified on the Pipfile, so you just need to run pipenv install and that will automatically create a virtual environment that you can activate with a pipenv shell.

Using `pip`

It's highly recommended to use a virtualenvironment to avoid conflict with other packages that are already installed: pip install virtualenv.

Create an environment: virtualenv env,
Activate the environment: source env/bin/activate (on Windows: source env\Scripts\activate.bat)
Install the requirements: pip install -r requirements.txt

Contributing to the scripts

You can verify if the styling of a script complaint with PEP8, with a couple of exceptions:

Install flake8 (pip install flake8) and run it on the script you want to test:

flake8 <file>.py --ignore=E501,E266,W503

E501: Line too long (82>79 characters),
E266: Too many leading '#' for block comment,
W503: Line break occurred before a binary operator)

You can also modify the file with an automatic formatter, like black (pip install black), and execute it:

black -l 100 <file>.py

Using Qt's maximum line length, 100.