qt5base-lts/util/cmake
Lucie Gérard 05fc3aef53 Use SPDX license identifiers
Replace the current license disclaimer in files by
a SPDX-License-Identifier.
Files that have to be modified by hand are modified.
License files are organized under LICENSES directory.

Task-number: QTBUG-67283
Change-Id: Id880c92784c40f3bbde861c0d93f58151c18b9f1
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
2022-05-16 16:37:38 +02: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 Use SPDX license identifiers 2022-05-16 16:37:38 +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 Use SPDX license identifiers 2022-05-16 16:37:38 +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
pro2cmake.py Use SPDX license identifiers 2022-05-16 16:37:38 +02: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
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