aboutsummaryrefslogtreecommitdiffstats
path: root/create_wheels.py
Commit message (Collapse)AuthorAgeFilesLines
* tools: add pyside6-qmlShyamnath Premnadh2022-06-141-0/+1
| | | | | | | | | | | | | | | | | - pyside6-qml is a tool that mimics the capabilities of qml utility and enables quick prototyping for qml files. Most cli options of the qml tool are carried forward to this tool. example-usage: pyside6-qml -a gui examples/declarative/editingmodel/main.qml To see all the cli options available with this tool, do: pyside6-qml --help Task-number: PYSIDE-1878 Pick-to: 6.3 Change-Id: I98bd77ccf6a0a286bb54da264312e81bf2964dc7 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Use SPDX license identifiersLucie Gérard2022-05-271-44/+8
| | | | | | | | | | | 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: I065150015bdb84a3096b5b39c061cf0a20ab637d Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
* build: add project tool to create_wheels.pyCristián Maureira-Fredes2022-04-181-0/+1
| | | | | | | | The tool was left out the new script to create wheels. Pick-to: 6.3 Change-Id: I858303fe359b622f35f3311584da0be3b5e3c6ce Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* build: script to create wheelsCristián Maureira-Fredes2022-03-291-0/+417
This approach intends to avoid modifying the current structure we have in build_scripts, and can replace the call: python setup.py bdist_wheel mainly encouraged by PEP517, and the need of having incremental wheels, to replace the current single PySide6 one. The current configuration allows to create two new wheels: PySide6_Essentials, and PySide6_Addons that contain all the essential and addons Qt modules defined by the Qt Installer tool, with some modifications due to the dependencies of certain tools. Check the README files for more info. The known PySide6 wheel is also generated, but it's empty in favor of using the previous two wheels as requirements, installing them automatically, to avoid modifying the usage of 'pip install pyside6' The strategy is based on the current logic behing 'prepare_packages' that we have been using. Once the modules are built, instead of removing those directories currently in 'build/your_env/package', we rename them. Inside this new directory, one can have the 'shiboken6', 'shiboken6_generator', and 'PySide6' directories, with eveything already packed with the required wheel structure. The main difference is that instead of using the content of PySide6 to build one build, we select some files with the MANIFEST.in to create another wheel. The wheel tag drops the old assumption of needing: cp36.cp37.cp38.cp39.cp310-abi3 and only uses: cp36-abi3 Additionally, for Linux, we follow PEP600 to use the GLIBC version in the wheel name instead of manylinux1, manylinux2010, etc... For the current CI configuration, we know we are using 2.28, which is the minimum supported version for Qt6, so the wheel will look like: PySide6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl The coin scripts were configured as well, to add the call of the new create_wheels.py script, and test them via wheel_tester.py Note: This script is not intended to be used as a general purpose wheel creation tool, and it's purely focused on the current Qt CI. There are many ad-hoc configurations used in different functions, like the structure of a Qt installation, the usage of 'a' on the environment for limited-api, etc. Task-number: PYSIDE-1115 Fixes: PYSIDE-692 Change-Id: Ic12e428b8b9b64bbe2facb1c520595ccd2384497 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>