[Development] Change to QUIP 7
Hi, we'd like to change the format of qt_attribution.json files a tiny bit. Currently, the Copyright key takes a string as value, and for readability purposes we used invalid JSON like this: "Copyright": "Copyright (C) 2002, 2003 CodeFactory AB Copyright (C) 2004, 2005 Red Hat, Inc." We would like to allow string arrays as value of this key to make the JSON files valid: "Copyright": [ "Copyright (C) 2002, 2003 CodeFactory AB", "Copyright (C) 2004, 2005 Red Hat, Inc." ] The change to QUIP 7 is here: https://codereview.qt-project.org/c/meta/quips/+/500993 and this email is the invitation of the community for discussion. Cheers, Joerg -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Failed to build Qt6 Documentation from qt/qtbase sources?
On 8/1/23 14:22, Haowei Hsu wrote: However, it turns out that there is an error in the Step 7: You're doing a prefix build [1] but you did not build & install before building the docs. The error indicates a missing file in the install prefix. Try a non-prefix build instead. Without configure, you can enable that by setting FEATURE_developer_build=ON. Best, Joerg [1] https://wiki.qt.io/Qt_Build_System_Glossary#Prefix_Build [2] https://wiki.qt.io/Qt_Build_System_Glossary#Non-prefix_Build -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] QUIP 18: License specification in Qt's modules
On 2/15/23 14:46, Jörg Bornemann via Development wrote: we're proposing a new QUIP: License specification in Qt's modules Please review https://codereview.qt-project.org/c/meta/quips/+/436096 And because QUIP 3 suggests that the initial text is also sent to the mailing list - here's the document attached. Cheers, JoergQUIP: 18 Title: License specification in Qt's modules Author: Lucie Gerard, Jörg Bornemann Status: Active Type: Informational Created: 2022-09-26 Post-History: https://lists.qt-project.org/pipermail/development/2023-February/043648.html Overview This QUIP specifies the licenses that are used in different parts of a typical Qt module repository and also provides helpful guidance about how to express which license source code is under. Note that repositories may deviate from this guideline. Check with the authors and copyright holders of the repository in question. Much of this document overlaps with the "Permitted Licenses in the Qt Free Edition" section of the KDE Software License Agreement [4]_. Please keep this document in sync with the KDE Software License Agreement. License header format = The license header follows the SPDX standard [0]_. There is a Copyright line and a license expression line:: Copyright (C) 2023 The Qt Company Ltd. SPDX-License-Identifier: The copyright line for code written by contributors outside the Qt Company can include that person's name (or legal entity they represent) in the Copyright header. Multiple copyright lines are possible. The `` must be a valid expression, according to the SPDX standard as defined in [1]_. The license identifiers used in a license expression are either from the list of known licenses [2]_ or prefixed with `LicenseRef-`. The license files are placed into a `LICENSES` directory below the Qt module repository's root. The license files are named after the SPDX license identifier followed by ``.txt`` [3]_. Parts of a Qt module repository === This sections defines the different parts of a Qt module repository. Module and plugin implementation Source files that belong to the implementation of Qt modules and plugins. The usual locations for module source code are the subdirectories ``src`` and ``plugins``. Examples Source files that belong to the implementation of Qt examples. The usual locations for examples is the ``examples`` subdirectory. Tests - Source files that belong to the implementation of Qt tests. The usual location is the ``tests`` subdirectory. Tools - Source files that belong to the implementation of Qt tools. The usual location is the ``tools`` subdirectory. Documentation - All ``.qdoc``, ``.qdocinc`` and ``.qdocconf`` files that are needed to generate the documentation. The usual locations for such files are ``doc`` directories all over the Qt module repository's directory tree. Documentation snippets -- Any source code that appears in the documentation. The usual locations are ``doc/snippets`` directories throughout the Qt module repository's directory tree. Build System Files -- All files that contribute to Qt's build system. That includes the following file name patterns: - ``CMakeLists.txt`` - ``*.cmake`` - ``*.pro`` - ``*.pri`` - ``*.prf`` License identifiers per repository part === Different parts of a Qt module repository are licensed differently. The following table lists the SPDX license expressions that should be used and where. ++--+ | Qt repository part | SPDX License Expression | ++==+ | Module and plugin | ``LicenseRef-Qt-Commercial OR LGPL-3.0-only``| | implementation | ``OR GPL-2.0-only OR GPL-3.0-only`` | | (Qt Essentials)| | ++--+ | Module and plugin | | ``LicenseRef-Qt-Commercial OR GPL-3.0-only`` | | implementation | || | (Qt Add-ons) | | *alternatively:* | || | ``LicenseRef-Qt-Commercial OR LGPL-3.0-only`` | || ``OR GPL-2.0-only OR GPL-3.0-only``| ++--+ | Examples | ``LicenseRef-Qt-Commercial OR BSD-3-Clause`` | ++--+ | Documentation | ``LicenseRef-Qt-Commercial`` | || ``OR GFDL-1.3-no-invariants-only``
Re: [Development] Sub-arch optimisations (was: How qAsConst and qExchange lead to qNN)
On 11/21/22 03:38, Thiago Macieira wrote: I've just finished a qtbase build on Linux with two sub-architectures and the symbol comparison of all the resulting libraries has shown zero difference. Tomorrow I will test all other modules (except qtwebengine). The code is ugly, so I'd appreciate guidance from the CMake experts. I've already submitted a few preliminary clean-ups. Are the changes that enable multi subarch builds already up? I did not manage the find them. Cheers, Joerg ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
