qt5base-lts/util/cmake
Amir Masoud Abdol b171abe695 Remove GENERATE_METATYPES
It doesn't seem like that it is being used anymore, except an instance
in pro2cmake which I replaced by NO_GENERATE_METATYPES.

Pick-to: 6.5
Change-Id: I135cf47e6041e98b354fb684f0079dad30689dea
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2023-01-18 14:47:12 +01:00
..
tests Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
.gitignore pro2cmake: GitIgnore .pro2cmake_cache 2020-10-16 14:53:02 +03:00
cmakeconversionrate.py CMake: Fix typos 2022-06-13 15:37:36 +02:00
condition_simplifier_cache.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
condition_simplifier.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
configurejson2cmake.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
generate_module_map.sh Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
helper.py xcb: use libxcb-cursor to replace Xlib/libXcursor 2022-09-06 11:21:43 +02:00
json_parser.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
Makefile CMake: pro2cmake: Fix errors reported by flake8 and mypy 2020-07-31 12:55:33 +02:00
Pipfile cmake scripts: add portalocker as dependency for Pipenv 2019-10-10 13:58:26 +00:00
pro2cmake.py Remove GENERATE_METATYPES 2023-01-18 14:47:12 +01:00
pro_conversion_rate.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
qmake_parser.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
README.md Remove the qmake2cmake wrapper scripts and document where they are 2022-04-12 10:34:40 +02:00
requirements.txt cmake scripts: format with black 2019-10-11 08:13:54 +00:00
run_pro2cmake.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00
special_case_helper.py Use SPDX license identifiers 2022-05-16 16:37:38 +02:00

CMake Utils

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

If you're looking to port your own Qt-based project from qmake to cmake, please use qmake2cmake.

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

If the pip install command above doesn't work, try:

python3.7 -m pip install -r requirements.txt

Contributing to the scripts

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

Install flake8 (pip install flake8) and run it on all python source files:

make flake8

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

make format