f67d8ae2d4
In Qt 5, qmake generates CMake Config files which expose the plugins as imported libraries. The name of these libraries are derived from the plugin class name. So QCocoaIntegrationPlugin, and not qcocoa. To keep compatibility between Qt5 and Qt6 CMake target names, the pro2cmake script should generate plugin target names based on the plugin class names. To avoid passing the same name in qt_add_plugin (target and CLASS_NAME), derive the class name from the target if the class name is not explicitly specified. Also add a new OUTPUT_NAME parameter which is used to change the final file name of the plugin, so that it's compatible with Qt5. For example to generate a qcocoa.dylib file, instead of QCocoaIntegrationPlugin.dylib file. The same OUTPUT_NAME value will be used for generation of plugin .prl files for qmake consumption. Change-Id: I4d53e680d7beb62befecd359cdf6bba60a34ff0d Reviewed-by: Qt CMake Build Bot Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> |
||
---|---|---|
.. | ||
tests | ||
cmakeconversionrate.py | ||
condition_simplifier_cache.py | ||
condition_simplifier.py | ||
configurejson2cmake.py | ||
generate_module_map.sh | ||
helper.py | ||
json_parser.py | ||
Makefile | ||
Pipfile | ||
pro2cmake.py | ||
pro_conversion_rate.py | ||
qmake_parser.py | ||
README.md | ||
requirements.txt | ||
run_pro2cmake.py | ||
special_case_helper.py |
CMake Utils
This directory holds scripts to help the porting process from qmake
to cmake
for Qt6.
Requirements
- Python 3.7,
pipenv
orpip
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.